[teiid-issues] [JBoss JIRA] (TEIID-3223) An issue with time in WHERE clause - SQLServer

[Steven Hawkins (JIRA)]

    [ https://issues.jboss.org/browse/TEIID-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13020825#comment-13020825 ] 

Steven Hawkins commented on TEIID-3223:
---------------------------------------

Actually that is still happening with their latest driver as well, so that will need a fix.

To recap it is expected with SQL Server 2005 and older that if you have a source model with a time type, that we will convert that to the representative datetime since those versions of SQL Server lack a time type - this is somewhat legacy behavior as we should avoid doing type manipulation at the source model as it's more correct to introduce a view layer.  For SQL Server 2008 and later the logic expects the source time to be a time value is currently putting non-bind literal timestamp values in as the JDBC escape value {t '....'} - which does work against JTDS.  However the SQL Server 4.0 driver up to the latest (4.0.2206.100) will convert the time escape instead into a timestamp and cause an exception.

> An issue with time in WHERE clause - SQLServer
> ----------------------------------------------
>
>                 Key: TEIID-3223
>                 URL: https://issues.jboss.org/browse/TEIID-3223
>             Project: Teiid
>          Issue Type: Bug
>    Affects Versions: 8.7.1
>         Environment: OS: fedora20
> arch: x86_64
> java: oracle 1.7
>            Reporter: Juraj Duráni
>            Assignee: Steven Hawkins
>
> Teiid is not able to manage WHERE clause with time value.
> translator: sqlserver
> base DB: SQL Server 2012/2008/2005



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)