[
https://issues.jboss.org/browse/TEIID-3223?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-3223:
---------------------------------------
I believe what is happening then is that the database type is not a time type for 2008 and
2012. There is compensation logic for 2005 and older to have columns modeled as time
type, but be effectively mapped to a timestamp (as there was no time type). But with later
SQL Servers we expect that if you use the time type the source column will be a time type
- otherwise there is a likely a mismatch in that SQL Server assumes a default date of
1900-01-01 vs. JDBC which assumes 1970-01-01.
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)