|
If the CallableStatement is closed before the isolation level is changed, it works in embedded mode, but it still fails the same way in client/server mode.
Adding 10.3.2.2 and 10.4.0.0 as fix versions as it looks like a candidate for merging to 10.3
Attaching derby-3496.diff which incorporates the new test case attached earlier.
The fix looks correct to me, but the new line in EmbedCallableStatement is not indented correctly (probably due to incorrect tab size setting in your IDE).
Committed revision 640787.
I did fix the indentation problem before committing. The "IDE" in question is 'vi'. :set hardtabs=4 (perhaps followed by :set autoindent) appears to be the magic words. Need to merge it to release branch
Merged to 10.4 in revision 640801.
Merged to 10.3 with revision 640808.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
$ java junit.textui.TestRunner org.apache.derbyTesting.functionTests.tests.jdbcapi.CallableTest
....E.............E.........
Time: 6.071
There were 2 errors:
1) testIsolationLevelChangeAfterFunctionCall(org.apache.derbyTesting.functionTests.tests.jdbcapi.CallableTest)java.sql.SQLException: Invalid transaction state - held cursor requires same isolation level
....
2) testIsolationLevelChangeAfterFunctionCall(org.apache.derbyTesting.functionTests.tests.jdbcapi.CallableTest)java.sql.SQLException: Invalid transaction state - held cursor requires same isolation level
....