[
https://issues.jboss.org/browse/TEIID-5295?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-5295:
---------------------------------------
[~jmartisk] Are you modeling the time type directly, or do you have a view layer
converting to time? MongoDB does not directly support a time type, so the behavior will
likely not be as expected unless using a view.
Comparisons of timestamps don't work correctly for MongoDB
----------------------------------------------------------
Key: TEIID-5295
URL:
https://issues.jboss.org/browse/TEIID-5295
Project: Teiid
Issue Type: Bug
Components: Misc. Connectors
Affects Versions: 8.12.11.6_4
Reporter: Jan Martiska
Assignee: Steven Hawkins
Examples of queries which don't behave as expected when running against MongoDB:
{noformat}
SELECT BQT1.SmallA.TimeValue FROM BQT1.SmallA WHERE BQT1.SmallA.TimeValue >
'17:00:00'
{noformat}
returns ALL timevalues which are not null
{noformat}
SELECT BQT1.SmallA.TimeValue FROM BQT1.SmallA WHERE BQT1.SmallA.TimeValue <
'17:00:00'
{noformat}
returns NO timevalues even though there are some less than 17:00
{noformat}
SELECT BQT1.SmallA.TimeValue FROM BQT1.SmallA WHERE BQT1.SmallA.TimeValue =
'15:00:00'
{noformat}
returns nothing
{noformat}
SELECT BQT1.SmallA.IntKey FROM BQT1.SmallA WHERE BQT1.SmallA.TimeValue IN
(convert('05:00:00', time), convert('15:00:00', time))
{noformat}
returns nothing
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)