Bug 780983 (SOA-3454)

Summary: EDS Ingres as source - WHERE CLAUSE is not returning expected results in some cases
Product: [JBoss] JBoss Enterprise SOA Platform 5 Reporter: Warren Gibson <wgibson>
Component: EDSAssignee: Van Halbert <vhalbert>
Status: CLOSED WONTFIX QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 5.2.0.ER4   
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-3454
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-11-15 17:45:54 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
QT_Ingres10_Push.vdb none

Description Warren Gibson 2011-10-06 17:03:10 UTC 
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)
Comment 1 Warren Gibson 2011-10-06 17:03:55 UTC 
Attachment: Added: QT_Ingres10_Push.vdb
Comment 2 Van Halbert 2011-10-06 17:26:55 UTC 
Link: Added: This issue Cloned to SOA-3458
Comment 3 Van Halbert 2011-10-11 12:46:27 UTC 
Link: Added: This issue relates to TEIID-1774
Comment 4 Van Halbert 2011-10-11 12:52:48 UTC 
Workaround Description: Added: The workaround would be to model the column as timestamp and cast to time.
Workaround: Added: Workaround Exists
Comment 5 Van Halbert 2011-10-11 12:57:16 UTC 
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.
Comment 6 Van Halbert 2011-10-11 13:00:23 UTC 
Link: Added: This issue relates to SOA-3453