[
https://issues.jboss.org/browse/TEIID-4228?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-4228:
---------------------------------------
On the Teiid side there are a couple of considerations:
Do we add a validation warning/error when the precision is non-positive on a numeric
type?
And/or do we add a workaround specifically for the odbc layer
Since this only affects one odbc usage scenario and only for a regression in metadata
load, I don't want to over do this on the Teiid side.
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)