[teiid-issues] [JBoss JIRA] (TEIID-4446) Rationalize precision/scale

[Steven Hawkins (JIRA)]

     [ https://issues.jboss.org/browse/TEIID-4446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steven Hawkins resolved TEIID-4446.
-----------------------------------
    Resolution: Done


Updated the code so that we are consistently handling precision/scale.  A nominal internal max of max short was introduced as the max precision (half that for scale) when precision is left unspecified - as those are safe for jdbc/odbc/odata metadata (jdbc expects a short scale, and odbc can only properly encode unsigned short).  However for backwards compatibility at for now we won't throw an exception if larger values are set.

> Rationalize precision/scale
> ---------------------------
>
>                 Key: TEIID-4446
>                 URL: https://issues.jboss.org/browse/TEIID-4446
>             Project: Teiid
>          Issue Type: Quality Risk
>          Components: OData, ODBC, Query Engine
>            Reporter: Steven Hawkins
>            Assignee: Steven Hawkins
>             Fix For: 9.1
>
>
> Our handling of precision/scale is inconsistent.  There are assumptions being made in the JDBC client, types.dat, the parser, and other paths that need to be explicit and consistent.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)