Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Duplicate
-
None
-
Normal
-
Release Note Needed, Repro attached
-
Embedded/Client difference
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)
Attachments
Issue Links
- is duplicated by
-
DERBY-4314 With derby client setTransactionIsolation executes and commits even if isolation has not changed
- Closed
-
DERBY-2401 change client setTransactionIsolation to only commit when the isolation level is changed to match embedded
- Closed
- is part of
-
DERBY-310 Document and/or change Derby client code to match behavior with Embedded driver where possible.
- Closed
- is related to
-
DERBY-638 Network driver setTransactionIsolation() causes a commit, but does not complete it locally
- Closed
- relates to
-
DERBY-2060 SET CURRENT ISOLATION in ref.man refers java.sql.Connection.setTransactionLevel instead of java.sql.Connection.setTransactionIsolation
- Closed