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

[ https://issues.jboss.org/browse/TEIID-4228?page=com.atlassian.jira.plugin... ] Debbie Steigner edited comment on TEIID-4228 at 6/29/16 3:20 PM: ----------------------------------------------------------------- I tested with an old Teiid Designer (9.0.1) and a Microsoft SQL Server column with numeric(9,2) imports with precision of 9 and scale of 2, but in 9.0.7 and 10.0 beta precision is 0, scale is still 2. Looks like for other reasons the default precision of bigdecimal was changed to 0 in 9.0.5 Teiid Designer - https://issues.jboss.org/browse/TEIIDDES-2746 but that is if it isn't specified and it is on the MSSQL side. I log a Designer bug for this https://issues.jboss.org/browse/TEIIDDES-2865 was (Author: dsteigne): I tested with an old Teiid Designer (9.0.1) and a Microsoft SQL Server column with numeric(9,2) imports with precision of 9 and scale of 2, but in 9.0.7 and 10.0 beta precision is 0, scale is still 2. Looks like for other reasons the default precision of bigdecimal was changed to 0 in 9.0.5 Teiid Designer - https://issues.jboss.org/browse/TEIIDDES-2746 but that is if it isn't specified and it is on the MSSQL side. I'll log a Designer bug on this. -- This message was sent by Atlassian JIRA (v6.4.11#64026)