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

[Steven Hawkins (JIRA)]

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

Steven Hawkins commented on TEIID-4228:
---------------------------------------

Just to confirm this seems to affect only teiid bigdecimal types that have been marked as having a precision of 0 correct?  It is generally invalid to have the precision set to 0 - was this something created by the user or by teiid through import?

> 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
>         Environment: Connections through ODBC driver
>            Reporter: Marc Shirley
>            Assignee: Steven Hawkins
>
> 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)