[teiid-issues] [JBoss JIRA] Resolved: (TEIID-741) SQL Server type hadling issues

[Steven Hawkins (JIRA)]

     [ https://jira.jboss.org/jira/browse/TEIID-741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steven Hawkins resolved TEIID-741.
----------------------------------

    Resolution: Done


Resolved as part of TEIID-806.  We default our SQL Server/Sybase byte handling to the smallint type rather than tinyint and the char type was updated to map to char(1).

> SQL Server type hadling issues
> ------------------------------
>
>                 Key: TEIID-741
>                 URL: https://jira.jboss.org/jira/browse/TEIID-741
>             Project: Teiid
>          Issue Type: Bug
>          Components: JDBC Connector
>    Affects Versions: 6.0.0
>            Reporter: Steven Hawkins
>            Assignee: Steven Hawkins
>             Fix For: 6.2.0
>
>
> If we pushdown a convert(stringvalue, char) function, it turns into the source expression convert(char, stringvalue), which has the following problems:  it defaults to type char(30) which is right padded, it is not trimmed since the target type was Char and the trim logic looks only for String.  Also it does not account for empty string mapping to null.
> The SQL Server tinyint type is unsigned.  Our import needs to be modified to this to short, since our byte type is unsigned.  Pushing down a convert(numericvalue, byte) as convert(tinyint, numericvalue) is problematic if the byte values are stored in a signed manner.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira