db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] Created: (DERBY-4314) With derby client setTransactionIsolation executes and commits even if isolation has not changed
Date Fri, 17 Jul 2009 20:46:14 GMT
With derby client setTransactionIsolation executes and commits even if isolation has not changed

-------------------------------------------------------------------------------------------------

                 Key: DERBY-4314
                 URL: https://issues.apache.org/jira/browse/DERBY-4314
             Project: Derby
          Issue Type: Improvement
          Components: JDBC, Network Client
    Affects Versions: 10.5.1.1, 10.4.2.0, 10.3.3.0, 10.2.2.0, 10.1.3.1, 10.6.0.0
            Reporter: Kathey Marsden
            Priority: Minor


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.


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message