Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <2020356.1163607758488.JavaMail.jira@brutus>
Date: Wed, 15 Nov 2006 08:22:38 -0800 (PST)
From: "Kim Haase (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_12450090 ] 
            
Kim Haase commented on DERBY-2060:
----------------------------------

I will fix this source file (rrefsqlj41180.dita) to change setTransactionLevel to setTransactionIsolation. I can also change the first sentence to correct the statement name from SET CURRENT ISOLATION LEVEL to SET CURRENT ISOLATION and fix the index entry as well.

I notice, though, that in the Developer's Guide section "Isolation levels and concurrency" (cdevconcepts15366.dita), the method name is Connection.setIsolationLevel, which appears to be incorrect too.  

Should I correct this as well? I'll assume so and provide patches for both files unless I hear otherwise.

I also see that in the "SQL error messages and exceptions" section of the Reference Manual (rrefexcept71493.dita), the method name is Connection.setTransactionIsolationLevel. This must be an error in the message text itself, so that would have to be fixed somewhere else and the DITA file would then have to be regenerated (I think). Would that be a separate bug?


> 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