[teiid-issues] [JBoss JIRA] Commented: (TEIID-360) SQLServer SQLTranslator issues

[ https://jira.jboss.org/jira/browse/TEIID-360?page=com.atlassian.jira.plug... ] Steven Hawkins commented on TEIID-360: -------------------------------------- This was forced due to the change in this issue of the time literal year to 1970 rather than 1900. There were other situations that would fail using the 1900 approach, since the engine assumes that the conversion of time to timestamp uses the year 1970 and connector prepared statement binds of time values use 1970 as well. The rationale for the change to 1970 and the proposed workaround above was to ensure consistency in all situations - without putting undo effort in the connector level. The follow-on issues to that suggested fix are that the sql server translator needs to support timestampadd and it would be good to have the rewriter understand how to invert the timestampadd function. Also since anyone following the fix won't be affected, I will change back the time literal translation back to 1900 to support legacy usage (however I suspect that this is a bit of an internally manufactured issue). -- 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