[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:all-tabpanel ]

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


Addressed as part of TEIID-4446.  For backwards compatibility we aren't prohibiting a 0 precision - except from the ddl parser.  If the value is 0 on the metadata object, then we'll report a consistent precision from odbc based upon a nominal max of 32767.

> 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
(v6.4.11#64026)