db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kim Haase (JIRA)" <j...@apache.org>
Subject [jira] Assigned: (DERBY-2060) SET CURRENT ISOLATION in ref.man refers java.sql.Connection.setTransactionLevel instead of java.sql.Connection.setTransactionIsolation
Date Wed, 15 Nov 2006 15:56:38 GMT
     [ http://issues.apache.org/jira/browse/DERBY-2060?page=all ]

Kim Haase reassigned DERBY-2060:
--------------------------------

    Assignee: Kim Haase

> 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
>         Assigned To: Kim Haase
>
> 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