[
https://issues.jboss.org/browse/TEIID-5311?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-5311.
-----------------------------------
Resolution: Done
Committed the changes, but did not explicitly document at this point. This only affects
string literals and nothing else. This is somewhat of a one-off as there are quite a few
formats supported by sybase.
Sybase implicit Convertion of String value 'yyyy-MM-dd HH:mm'
into a Date value Causes mismatches in JDV Date comparison
------------------------------------------------------------------------------------------------------------------------
Key: TEIID-5311
URL:
https://issues.jboss.org/browse/TEIID-5311
Project: Teiid
Issue Type: Enhancement
Components: Query Engine
Reporter: Anu Saji
Assignee: Steven Hawkins
Priority: Minor
Fix For: 11.2
Attachments: eniqpreparser_v4.zip
Sybase implicitly converts a String value 'yyyy-MM-dd HH:mm' into a Date value.
This format is not standard and this conversion is specific to Sybase.
As JDBC/Java standard, JDV implicitly converts
'yyyy-MM-dd HH:mm:ss' into a Timestamp value
'yyyy-MM-dd' into a Date value
So JDV does not considered 'yyyy-MM-dd HH:mm' as a Date value and does not
proceed to any implicit conversion. 'yyyy-MM-dd HH:mm' remains like a String
value which partially matches with Date comparison
Constraint
We cannot modify the incoming query
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)