Hide Forgot
Workaround: Workaround Exists Workaround Description: The workaround would be to model the column as timestamp and cast to time. project_key: SOA EDS Query Testing is getting unexpected results on 24 queries involving WHERE CLAUSE. A few examples queries are given below: SELECT BQT1.SmallA.TimeValue FROM BQT1.SmallA WHERE BQT1.SmallA.TimeValue > '17:00:00' ORDER BY TimeValue (Expected 11 records but received 23) SELECT INTKEY, FLOATNUM FROM BQT1.SmallA WHERE RIGHT(FLOATNUM, 1) <> 0 ORDER BY INTKEY (Expected 43 records but received only 0) SELECT BQT1.SmallA.StringKey, BQT2.SmallB.FloatNum FROM BQT1.SmallA, BQT2.SmallB WHERE BQT1.SmallA.StringKey = convert(BQT2.SmallB.FloatNum, string) AND BQT1.SmallA.IntKey >= 0 AND BQT2.SmallB.IntKey >= 0 ORDER BY BQT1.SmallA.StringKey (Expected 25 records but received only 0) SELECT IntKey, TimeValue FROM (SELECT IntKey, TimeValue FROM BQT2.SmallA WHERE IntKey > 5) AS x WHERE TimeValue >= '17:00:00' ( Expected 13 records but received 20)
Attachment: Added: QT_Ingres10_Push.vdb
Link: Added: This issue Cloned to SOA-3458
Link: Added: This issue relates to TEIID-1774
Workaround Description: Added: The workaround would be to model the column as timestamp and cast to time. Workaround: Added: Workaround Exists
If this becomes an issue, further investigation can be done to try to fix handling the native type differently. But at this time, the engineer doesn't feel this use case needs to be fixed at this time.
Link: Added: This issue relates to SOA-3453