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

Derby

Network client setTransactionIsolation() commits any active transactions

Created: 09/Nov/06 08:53 AM Updated: 19/Jul/09 07:03 PM

Return to search

Component/s:

Network Client

Affects Version/s:

None

Fix Version/s:

None

Time Tracking:

Not Specified

Issue Links:

Duplicate

This issue is duplicated by:

DERBY-4314 With derby client setTransactionIsolation executes and commits even if isolation has not changed

~~DERBY-2401~~ change client setTransactionIsolation to only commit when the isolation level is changed to match embedded

Incorporates

This issue is part of:

~~DERBY-310~~ Document and/or change Derby client code to match behavior with Embedded driver where possible.

Reference

This issue relates to:

~~DERBY-2060~~ SET CURRENT ISOLATION in ref.man refers java.sql.Connection.setTransactionLevel instead of java.sql.Connection.setTransactionIsolation

This issue is related to:

~~DERBY-638~~ Network driver setTransactionIsolation() causes a commit, but does not complete it locally

Urgency:	Normal
Issue & fix info:	Repro attached, Release Note Needed
Bug behavior facts:	Embedded/Client difference

Description

« Hide

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)

All

Comments

Work Log

Change History

Subversion Commits

Sort Order:

No work has yet been logged on this issue.