db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bernt M. Johnsen (JIRA)" <j...@apache.org>
Subject [jira] Created: (DERBY-2060) SET CURRENT ISOLATION in ref.man refers java.sql.Connection.setTransactionLevel instead of java.sql.Connection.setTransactionIsolation
Date Wed, 08 Nov 2006 22:30:51 GMT
SET CURRENT ISOLATION in ref.man refers java.sql.Connection.setTransactionLevel instead of
java.sql.Connection.setTransactionIsolation
--------------------------------------------------------------------------------------------------------------------------------------

                 Key: DERBY-2060
                 URL: http://issues.apache.org/jira/browse/DERBY-2060
             Project: Derby
          Issue Type: Bug
          Components: Documentation
            Reporter: Bernt M. Johnsen


On SET CURRENT ISOLATION statement in the Derby refernce manual:

"Issuing this command commits the current transaction, which is consistent with the java.sql.Connection.setTransactionLevel
method."

The correct method name is java.sql.Connection.setTransactionIsolation (java.sql.Connection.setTransactionLevel
does not exist)

BTW: setTransactionIsolation will commit the current transaction if called in the client driver
but not in the embedded driver. See DERBY-638

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message