]
Steven Hawkins commented on TEIID-1283:
---------------------------------------
It looks like this can be caused if the first batch to the client contains only a single
row and the next batch has the wrong final row. I'll look into why that may be case.
Race condition results in bad resultset for query on union
----------------------------------------------------------
Key: TEIID-1283
URL:
https://jira.jboss.org/browse/TEIID-1283
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 7.1
Environment: MaxOS 10.6.4, JBoss 5.1.0
Reporter: Howard Abrams
Assignee: Steven Hawkins
Take a table, call it 'A', in a physical model backed by a database (DB2 on Z/OS
in this case)
Take a view, call it 'B', backed by a file connector
From JDBC, make the query:
Select * from (select * from A union select * from B) where foo='bar'.
where 'bar' is only found in B, not A.
Execute the query get back a resultset:
ResultSet r = statement.executeQuery();
but this code will fail with a "resultset cursor is after the last row"
if ( r.next )
String foo = r.getString(1);
but this code will work correctly:
Thread.sleep(1000);
if ( r.next )
String foo = r.getString(1);
Putting the union in a materialized view also works.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: