[DERBY-2064] Network client setTransactionIsolation() commits any active transactions

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Fix Version/s: 10.7.1.1
• Component/s: Network Client
• Labels: derby_triage10_5_2
• Urgency: Normal
• Issue & fix info: Release Note Needed, Repro attached
• Bug behavior facts: Embedded/Client difference
• Assignee: Unassigned
• Reporter: Bernt Johnsen
• Created: 09/Nov/06 08:53
• Updated: 17/Jun/13 09:19
• Resolved: 25/Aug/11 22:08

Description

Network client implements setTransactionIsolation() using
Statement.executeUpdate("SET CURRENT ISOLATION.......")
which again causes any active transactions to commit.

This differs from the embedded driver, where setTransactionIsolation() does not cause a commit.

(Note that "SET CURRENT ISOLATION....." will commit active transactions idependent of this)

Issue Links

• is duplicated by: DERBY-4314 With derby client setTransactionIsolation executes and commits even if isolation has not changed
• is duplicated by: DERBY-2401 change client setTransactionIsolation to only commit when the isolation level is changed to match embedded
• is part of: DERBY-310 Document and/or change Derby client code to match behavior with Embedded driver where possible.
• is related to: DERBY-638 Network driver setTransactionIsolation() causes a commit, but does not complete it locally
• relates to: DERBY-2060 SET CURRENT ISOLATION in ref.man refers java.sql.Connection.setTransactionLevel instead of java.sql.Connection.setTransactionIsolation