[teiid-issues] [JBoss JIRA] Resolved: (TEIID-880) SQL Server uniqueidentifier handling

[Steven Hawkins (JIRA)]

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

Steven Hawkins resolved TEIID-880.
----------------------------------

    Resolution: Done


Added the cast as the fix.  However both this and the trim strings logic are too broadly applied.  In both cases we don't need the conversion applied in all circumstances.  That will be left to fix at a later time.

> SQL Server uniqueidentifier handling
> ------------------------------------
>
>                 Key: TEIID-880
>                 URL: https://jira.jboss.org/jira/browse/TEIID-880
>             Project: Teiid
>          Issue Type: Quality Risk
>          Components: JDBC Connector
>    Affects Versions: 6.0.0
>            Reporter: Steven Hawkins
>            Assignee: Steven Hawkins
>            Priority: Optional
>             Fix For: 6.3
>
>
> SQL Server's uniqueidentifier is typically imported as a string, but cannot be used in comparable operations (distinct, order by, group by).  Our designer cost analyzer logic already compensated for this, but a more general fix would be to wrap the uniqueidentifier as cast(col as char(36)), which would be safe.

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