[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 reassigned TEIID-4228:
-------------------------------------

          Component/s: ODBC
        Fix Version/s: 9.x
             Priority: Minor  (was: Major)
    Affects Version/s: 8.7
             Assignee:     (was: Steven Hawkins)


Lowering the priority of this as we are recommending with TEIID-4229 that parse statements not be used and 0 is an invalid precision.  We should still investigate if we want to validate against that (possibly only for odbc) and where the 0 value is coming from.  Marc - any updates from the customer side will help with that.

> 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
>            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)