Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <10410111.1164663082262.JavaMail.jira@brutus>
Date: Mon, 27 Nov 2006 13:31:22 -0800 (PST)
From: "Bernt M. Johnsen (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-2060) SET CURRENT ISOLATION in ref.man
 refers java.sql.Connection.setTransactionLevel instead of
 java.sql.Connection.setTransactionIsolation
In-Reply-To: <22807930.1163025051563.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

    [ http://issues.apache.org/jira/browse/DERBY-2060?page=comments#action_12453708 ] 
            
Bernt M. Johnsen commented on DERBY-2060:
-----------------------------------------

Great.  One comment though: in out/devguide/cdevconcepts15366.html it says "Issuing this command commits the current transaction, which is consistent with the java.sql.Connection.setTransactionIsolation method.".

In the current implementation, setTransactionIsolation() will commit the current transaction on the network driver, but not in the embedded driver. "SET CURRENT ISOLATION...." commits on both. See also DERBY-2064


> 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
>         Attachments: DERBY-2060.diff, DERBY-2060.zip
>
>
> 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