[ 
http://issues.apache.org/jira/browse/DERBY-694?page=comments#action_12426774 ] 
            
Rick Hillegas commented on DERBY-694:
-------------------------------------

I'm afraid that I see the following diff in the jdbc4 tests now. I ran this on 
linux.

********* Diff file 
derbyall/derbynetmats/DerbyNet/jdbcapi/ResultSetCloseTest.diff
*** Start: ResultSetCloseTest jdk1.4.2_08 DerbyNet derbynetmats:jdbcapi 
2006-08-08 10:29:26 ***
0 add
> .E
> There was 1 error:
> 1) 
> testResultSetDoesNotClose(org.apache.derbyTesting.functionTests.tests.jdbcapi.ResultSetCloseTest)com.ibm.db2.jcc.c.SqlException:
>  Invalid operation: result set closed
> FAILURES!!!
> Tests run: 1,  Failures: 0,  Errors: 1
Test Failed.


> Statement exceptions cause all the connection's result sets to be closed with 
> the client driver
> -----------------------------------------------------------------------------------------------
>
>                 Key: DERBY-694
>                 URL: http://issues.apache.org/jira/browse/DERBY-694
>             Project: Derby
>          Issue Type: Bug
>          Components: Network Client
>    Affects Versions: 10.1.1.1
>            Reporter: Oyvind Bakksjo
>         Assigned To: V.Narayanan
>            Priority: Minor
>         Attachments: DERBY-694.html, DERBY-694_upload_v1.diff, 
> DERBY-694_upload_v1.stat, DERBY-694_v2.diff, DERBY-694_v2.stat, 
> DERBY-694_v3.diff, DERBY-694_v3.stat, DERBY-694_v4.diff, DERBY-694_v4.stat, 
> DERBY-694_v5.diff, DERBY-694_v5.stat, StatementRollbackTest.java
>
>
> Scenario:
> Autocommit off. Have two prepared statements, calling executeQuery() on both, 
> giving me two result sets. Can fetch data from both with next(). If one 
> statement gets an exception (say, caused by a division by zero), not only 
> this statement's result set is closed, but also the other open resultset. 
> This happens with the client driver, whereas in embedded mode, the other 
> result set is unaffected by the exception in the first result set (as it 
> should be).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to