[
https://issues.apache.org/jira/browse/DERBY-3801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12898188#action_12898188
]
Yun Lee commented on DERBY-3801:
--------------------------------
You have commented:
"4. change of isolation level succeeds with client because cursor is already
closed.
Again, should the cursor be closed? It's really the same kind of issue as
of difference 3.
A new bug should be logged, the test case showing the difference should get
added to a different test, and the ij test script should be massaged so that
client and embedded give the same output. "
However, in testSetTransactionIsolationInHoldCursor() method of
org.apache.derbyTesting.functionTests.tests.jdbcapi.SetTransactionIsolationTest,,
" /**
* Call setTransactionIsolation with holdable cursor open?
*/
public void testSetTransactionIsolationInHoldCursor() throws SQLException
{
Connection conn = getConnection();
try {
PreparedStatement ps = conn.prepareStatement("SELECT * from TAB1");
ResultSet rs = ps.executeQuery();
rs.next();
// setTransactionIsolation should fail because we have
// a holdable cursor open
conn
.setTransactionIsolation(java.sql.Connection.TRANSACTION_SERIALIZABLE);
rs.next(); // to fix DERBY-1108. Else the GC for ibm15 will clean
// up the ResultSet Object
} catch (SQLException se) {
assertSQLState("Expected Exception if held cursor is open",
"X0X03", se);
return;
}
fail("FAIL: setTransactionIsolation() did not throw exception with open
hold cursor");
}"
Here, DERBY performs the same in both mode. Does the difference just occur in
IJ or is there any other configuration to trigger it?
> Convert "org.apache.derbyTesting.functionTests.tests.lang.holdCursorIJ.sql"
> to junit.
> --------------------------------------------------------------------------------------
>
> Key: DERBY-3801
> URL: https://issues.apache.org/jira/browse/DERBY-3801
> Project: Derby
> Issue Type: Improvement
> Components: Test
> Reporter: Junjie Peng
> Assignee: Yun Lee
> Attachments: derby-3801-1-patch.txt, derby-3801-2.patch,
> derby-3801-2.stat, derby-3801-4.patch, derby-3801-5.patch, derby-3801-5.stat,
> derby-3801-6.patch, derby-3801-6.stat, DERBY-3801-Tiago.patch
>
>
> Convert "org.apache.derbyTesting.functionTests.tests.lang.holdCursorIJ.sql"
> to junit.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
