[JBoss JIRA] Created: (TEIID-1283) Race condition results in bad resultset for query on union
by Howard Abrams (JIRA)
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: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 12 months
[JBoss JIRA] Created: (TEIID-1237) Stored procedures should allow for better use of inout/out/return values
by Steven Hawkins (JIRA)
Stored procedures should allow for better use of inout/out/return values
------------------------------------------------------------------------
Key: TEIID-1237
URL: https://jira.jboss.org/browse/TEIID-1237
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Affects Versions: 7.1
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 7.2
Teiid stored procedure command or assignment statements do not typically make use of inout/out/return values (the exception is if a resultset is not returned). It would be better to allow variables to be used in inout/out positions to capture the out values.
e.g. instead of
call proc(1)
just implicitly creating the result set to return,
a = call proc(1, b)
would also assign the return value to a and would set an out value to b.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 12 months
[JBoss JIRA] Created: (TEIID-1168) Query Testing - CLOB, LOB, etc is returning an object reference in CTC rather than returning the content of the object (content is needed for validation purposes)
by Warren Gibson (JIRA)
Query Testing - CLOB, LOB, etc is returning an object reference in CTC rather than returning the content of the object (content is needed for validation purposes)
------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: TEIID-1168
URL: https://jira.jboss.org/browse/TEIID-1168
Project: Teiid
Issue Type: Bug
Components: Integration Tests
Reporter: Warren Gibson
Assignee: Van Halbert
Query testing is returning an object reference for CLOB, LOB, etc. In the past these were returned as a string.
They should be converted to a string so the content can be validated.
Examples:
Query: SELECT * FROM XQTDoc.BQTDocTestDocument
>
> <actual_queryResults>
> <select>
> <dataElement type="xml">xml</dataElement>
> </select>
> <table rowCount="1" columnCount="1">
> <tableRow>
> <tableCell>
> <object>org.teiid.core.types.SQLXMLImpl@be76c7</object>
> </tableCell>
> </tableRow>
> </table>
> </actual_queryResults>
>
>
> <expected_queryResults>
> <select>
> <dataElement type="xml">xml</dataElement>
> </select>
> <table rowCount="1" columnCount="1">
> <tableRow>
> <tableCell>
> <string><?xml version="1.0" encoding="UTF-8"?><xqt:BQTDocTest xmlns:xqt="http://www.metamatrix.com/XQTSchema"><SingleRow><IntKey>0</IntKey><StringKey>0</StringKey><IntNum/><StringNum>-24</StringNum><FloatNum>-24.0</FloatNum><LongNum>-24</LongNum><DoubleNum>-24.0</DoubleNum><ByteNum>-128</ByteNum><DateValue>2000-01-01</DateValue><TimeValue>00:00:00</TimeValue><TimestampValue>2000-01-01 00:00:00.0</TimestampValue><BooleanValue>false</BooleanValue><CharValue>1</CharValue><ShortValue>-32768</ShortValue><BigIntegerValue>-24</BigIntegerValue><BigDecimalValue>-24</BigDecimalValue><ObjectValue>-24</ObjectValue></SingleRow><SingleRow><IntKey>1</IntKey><StringKey>1</StringKey><IntNum>-23</IntNum><StringNum/><FloatNum>-23.0</FloatNum><LongNum>-23</LongNum><DoubleNum>-23.0</DoubleNum><ByteNum>-127</ByteNum><DateValue>2000-01-02</DateValue><TimeValue>01:00:00</TimeValue><TimestampValue>2000-01-01 00:00:01.0</TimestampValue><BooleanValue>true< ......................
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 12 months