[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=13409353#comment-13409353 ] 

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

Designer should not allow you to set those values.  Precision can never be zero and scale can never be greater than precision.  For backwards compatibility the server is treating 0 as undefined precision and returning the max instead.  I'll have to double check if it's expected for us to then return as the scale.

> 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: Sub-task
>          Components: ODBC
>    Affects Versions: 8.7
>         Environment: Connections through ODBC driver
>            Reporter: Marc Shirley
>            Assignee: Steven Hawkins
>            Priority: Minor
>             Fix For: 9.1
>
>
> 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
(v7.2.3#72005)