Details
-
Type:
Improvement
-
Status: Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 10.1.3.1, 10.2.2.0, 10.3.3.0, 10.4.2.0, 10.5.1.1, 10.6.1.0
-
Fix Version/s: 10.7.1.1
-
Component/s: JDBC, Network Client
-
Labels:
-
Issue & fix info:Newcomer, Patch Available
-
Bug behavior facts:Embedded/Client difference
Description
With in EmbedConnection.setIsolation() we have a check to see if the isolation level is the same and if so just return without doing a commit:
public void setTransactionIsolation(int level) throws SQLException {
if (level == getTransactionIsolation())
return;
with org.apache.derby.client.am.Connection we have no such check. It would be good if the client driver acted like embedded.
Attachments
Issue Links
- duplicates
-
DERBY-2064 Network client setTransactionIsolation() commits any active transactions
-
- Closed
-
- is related to
-
DERBY-4343 ASSERT FAILED calling setTransactionIsolation checking isolation_ == level on pooled connection
-
- Closed
-