[DERBY-1035] With client, Connection.getTransactionIsolation() return value is wrong after changing the isolation level with an SQL statement such as "set current isolation = RS"

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 10.1.3.1, 10.2.1.6
• Fix Version/s: 10.1.3.1, 10.2.1.6
• Component/s: Network Client
• Assignee: Deepa
• Reporter: Katherine Marsden
• Created: 23/Feb/06 09:15
• Updated: 01/Jul/06 07:39
• Resolved: 06/Jun/06 23:57

Description

With client, if the isolation level is set with an SQL Statement such as "SET CURRENT ISOLATION = RS" the value of Connection.getTransactionIsolation() will not be correct.

jdbcapi/checkDataSource has tests for sending SQL statements to change the isolation level:

e.g.
s.executeUpdate("set current isolation = RS");
printState("SQL to change isolation in local", cs1);
I will disable these tests and reference this bug number.

It is not really clear how to handle this without parsing the statement on the client side.

Issue Links

• is part of: DERBY-1148 Client XA getTransactionIsolation() does not return the correct isolation level when rejoining a global transaction