[ https://issues.jboss.org/browse/TEIID-3223?page=com.atlassian.jira.plugin... ] 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. -- This message was sent by Atlassian JIRA (v6.3.8#6338)