[
https://jira.jboss.org/jira/browse/TEIID-969?page=com.atlassian.jira.plug...
]
Steve Hawkins resolved TEIID-969.
---------------------------------
Resolution: Out of Date
Teiid no longer has a specific method for determining this conversion. The rewriter will
push down a literal in the form of a timestamp for anything modeled as a timestamp (even
if it's a source time). We rely on the driver, such as datadirect, to handle the
conversion.
Time, date, and timestamp literals are being sent to Oracle as
to_timestamp() regardless of their data type
-----------------------------------------------------------------------------------------------------------
Key: TEIID-969
URL:
https://jira.jboss.org/jira/browse/TEIID-969
Project: Teiid
Issue Type: Bug
Components: JDBC Connector
Affects Versions: 6.0.0
Environment: MMServer 5.5.3
Oracle 10i
Oracle ANSI Connector
Reporter: Larry O'Leary
Assignee: Larry O'Leary
Fix For: 7.0
Attachments: mylyn-context.zip
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Source model uses a MetaMatrix type of timestamp and a native type of DATE. In prior
releases this seems to have resulted in literal values that are being compared to the
modeled column to be sent to Oracle as to_date(). Now, they are being sent as
to_timestamp() which results in indexes being ignoreed for columns that are of DATE type.
--
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