[teiid-issues] [JBoss JIRA] (TEIID-4228) ODBC "Parse Statements" option can result in changes in LENGTH metadata for columns

[Debbie Steigner (JIRA)]

    [ https://issues.jboss.org/browse/TEIID-4228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13258826#comment-13258826 ] 

Debbie Steigner edited comment on TEIID-4228 at 6/29/16 3:21 PM:
-----------------------------------------------------------------

I tested with an old Teiid Designer (9.0.1) and a Microsoft SQL Server column with numeric(9,2) imports with precision of 9 and scale of 2, but in 9.0.7 and 10.0 beta precision is 0, scale is still 2.  Looks like for other reasons the default precision of bigdecimal was changed to 0 in 9.0.5 Teiid Designer - https://issues.jboss.org/browse/TEIIDDES-2746 but that is if it isn't specified and it is on the MSSQL side.  I logged a Designer bug for this https://issues.jboss.org/browse/TEIIDDES-2865



was (Author: dsteigne):
I tested with an old Teiid Designer (9.0.1) and a Microsoft SQL Server column with numeric(9,2) imports with precision of 9 and scale of 2, but in 9.0.7 and 10.0 beta precision is 0, scale is still 2.  Looks like for other reasons the default precision of bigdecimal was changed to 0 in 9.0.5 Teiid Designer - https://issues.jboss.org/browse/TEIIDDES-2746 but that is if it isn't specified and it is on the MSSQL side.  I log a Designer bug for this https://issues.jboss.org/browse/TEIIDDES-2865


> ODBC "Parse Statements" option can result in changes in LENGTH metadata for columns
> -----------------------------------------------------------------------------------
>
>                 Key: TEIID-4228
>                 URL: https://issues.jboss.org/browse/TEIID-4228
>             Project: Teiid
>          Issue Type: Bug
>          Components: ODBC
>    Affects Versions: 8.7
>         Environment: Connections through ODBC driver
>            Reporter: Marc Shirley
>            Assignee: Steven Hawkins
>            Priority: Minor
>             Fix For: 9.x
>
>
> Connections through ODBC driver with the driver setting "Parse Statements" option enabled can result in incorrect length values being passed to the client.  In some cases (such as SQL Server linked server capabilities), this can result in the client throwing exceptions due to the expected LENGTH changing during the course of the query execution.
> This may be limited to columns with precision set to 0, as the SQL Server linked server case was corrected when the precision was changed from 0 to 9 for the column specified in the error.



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