[ http://issues.apache.org/jira/browse/DERBY-694?page=comments#action_12426850 ] V.Narayanan commented on DERBY-694: -----------------------------------
I ran the repro attached with the IBM JDBC Universal Driver. I had'nt done this before. I noticed that it showed behaviour similar to what is currently happening in the Derby ClientDriver (i.e.) a statement exception was causing all the connections result sets to be closed. Then I ran the test in the DerbyNet framework which is specific to the IBM JDBC Universal driver. As expected it failed. The failure seems to be specific to the DerbyNet framework and to the IBM JDBC Driver. I will overcome this by submitting a fresh patch that will exclude this test from running in the DerbyNet framework. thanx Narayanan > 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
