Return-Path: 
 <derby-commits-return-6025-apmail-db-derby-commits-archive=db.apache.org@db.apache.org>
Delivered-To: apmail-db-derby-commits-archive@www.apache.org
Received: (qmail 96386 invoked from network); 14 Dec 2006 07:50:17 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 14 Dec 2006 07:50:17 -0000
Received: (qmail 71271 invoked by uid 500); 14 Dec 2006 07:50:25 -0000
Delivered-To: apmail-db-derby-commits-archive@db.apache.org
Received: (qmail 71247 invoked by uid 500); 14 Dec 2006 07:50:25 -0000
Mailing-List: contact derby-commits-help@db.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:derby-commits-help@db.apache.org>
list-unsubscribe: <mailto:derby-commits-unsubscribe@db.apache.org>
List-Post: <mailto:derby-commits@db.apache.org>
Reply-To: "Derby Development" <derby-dev@db.apache.org>
List-Id: <derby-commits.db.apache.org>
Delivered-To: mailing list derby-commits@db.apache.org
Received: (qmail 71236 invoked by uid 99); 14 Dec 2006 07:50:24 -0000
Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Dec 2006 23:50:24 -0800
X-ASF-Spam-Status: No, hits=-9.4 required=10.0
	tests=ALL_TRUSTED,NO_REAL_NAME
X-Spam-Check-By: apache.org
Received: from [140.211.11.3] (HELO eris.apache.org) (140.211.11.3)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Dec 2006 23:50:16 -0800
Received: by eris.apache.org (Postfix, from userid 65534)
	id EF32A1A981A; Wed, 13 Dec 2006 23:49:30 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: svn commit: r487088 - in /db/derby/docs/trunk/src:
 devguide/cdevconcepts15366.dita devguide/cdevconcepts22300.dita
 ref/rrefjavcsti.dita ref/rrefsqlj41180.dita
Date: Thu, 14 Dec 2006 07:49:30 -0000
To: derby-commits@db.apache.org
From: kahatlen@apache.org
X-Mailer: svnmailer-1.1.0
Message-Id: <20061214074930.EF32A1A981A@eris.apache.org>
X-Virus-Checked: Checked by ClamAV on apache.org

Author: kahatlen
Date: Wed Dec 13 23:49:30 2006
New Revision: 487088

URL: http://svn.apache.org/viewvc?view=rev&rev=487088
Log:
DERBY-2060: SET CURRENT ISOLATION in ref.man refers
java.sql.Connection.setTransactionLevel instead of
java.sql.Connection.setTransactionIsolation

Patch contributed by Kim Haase.

Modified:
    db/derby/docs/trunk/src/devguide/cdevconcepts15366.dita
    db/derby/docs/trunk/src/devguide/cdevconcepts22300.dita
    db/derby/docs/trunk/src/ref/rrefjavcsti.dita
    db/derby/docs/trunk/src/ref/rrefsqlj41180.dita

Modified: db/derby/docs/trunk/src/devguide/cdevconcepts15366.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevconcepts15366.dita?view=diff&rev=487088&r1=487087&r2=487088
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevconcepts15366.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevconcepts15366.dita Wed Dec 13 23:49:30 2006
@@ -44,8 +44,19 @@
 locking out transactions. Lower isolation levels thus allow greater concurrency.</p>
 <p>Inserts, updates, and deletes always behave the same no matter what the
 isolation level is. Only the behavior of select statements varies.</p>
-<p>To set isolation levels you can use the JDBC <i>Connection.setIsolationLevel</i> method
-or the SQL SET ISOLATION statement. The names of the isolation levels are
+<p>To set isolation levels you can use the JDBC <i>Connection.setTransactionIsolation</i> method
+or the SQL SET ISOLATION statement.</p>
+<p>If there is an active transaction, the network client driver always commits 
+the active transaction, whether you use the JDBC 
+<i>Connection.setTransactionIsolation</i> method or the SQL SET ISOLATION 
+statement. It does this even if the method call or statement does not actually 
+change the isolation level (that is, if it sets the isolation level to its 
+current value). The embedded driver also always commits the active transaction 
+if you use the SET ISOLATION statement. However, if you use the 
+<i>Connection.setTransactionIsolation</i> method, the embedded driver commits 
+the active transaction only if the call to <i>Connection.setTransactionIsolation</i> 
+actually changes the isolation level.</p>
+<p>The names of the isolation levels are
 different, depending on whether you use a JDBC method or SQL statement. <xref
 href="#cdevconcepts15366/cdevconceptsiso_level"></xref> shows the equivalent
 names for isolation levels whether they are set through the JDBC method or
@@ -63,7 +74,7 @@
 </thead>
 <tbody>
 <row>
-<entry colname="colspec0">Connection.TRANSACTION_READ_ UNCOMMITTED (ANSI level
+<entry colname="colspec0">Connection.TRANSACTION_READ_UNCOMMITTED (ANSI level
 0)</entry>
 <entry colname="colspec1">UR, DIRTY READ, READ UNCOMMITTED </entry>
 </row>

Modified: db/derby/docs/trunk/src/devguide/cdevconcepts22300.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevconcepts22300.dita?view=diff&rev=487088&r1=487087&r2=487088
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevconcepts22300.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevconcepts22300.dita Wed Dec 13 23:49:30 2006
@@ -39,10 +39,13 @@
 within an SQL statement. For more information, see "SET ISOLATION statement"
 in the <cite><ph conref="devconrefs.dita#pub/citref"></ph></cite>. You can
 use the WITH clause to change the isolation level for the current statement
-only, not the transaction. For information about the"WITH clause," see the
-"SELECT statement"in the <cite><ph conref="devconrefs.dita#pub/citref"></ph></cite>. </p>
+only, not the transaction. For information about the WITH clause, see
+"SELECT statement" in the <cite><ph conref="devconrefs.dita#pub/citref"></ph></cite>. </p>
 <p> In all cases except when you change the isolation level using the WITH
-clause, changing the isolation level commits the current transaction.</p>
+clause, changing the isolation level commits the current transaction. In most
+cases, the current transaction is committed even if you set the isolation level
+in a way that does not change it (that is, if you set it to its current value).
+See <xref href="cdevconcepts15366.dita#cdevconcepts15366"></xref> for details.</p>
 <note>For information about how to choose a particular isolation level, see <cite><ph
 conref="devconrefs.dita#pub/cittuning"></ph></cite>.</note>
 </conbody>

Modified: db/derby/docs/trunk/src/ref/rrefjavcsti.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefjavcsti.dita?view=diff&rev=487088&r1=487087&r2=487088
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefjavcsti.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefjavcsti.dita Wed Dec 13 23:49:30 2006
@@ -30,8 +30,11 @@
  <i>java.sql.Connection.TRANSACTION_READ_COMMITTED, and </i><i>java.sql.Connection.TRANSACTION_READ_UNCOMMITTED</i> transaction
 isolations are available from a <ph conref="refconrefs.dita#prod/productshortname"></ph> database.</p></section>
 <section><p><i>TRANSACTION_READ_COMMITTED</i> is the default isolation level.</p></section>
-<section><p>Changing the current isolation for the connection with <i>setConnection</i> commits
-the current transaction and begins a new transaction, per the JDBC standard.</p></section>
+<section><p>Changing the current isolation for the connection with <i>setTransactionIsolation</i> commits
+the current transaction and begins a new transaction.
+For more details about transaction isolation, see "Locking, concurrency, and 
+isolation" in the 
+<cite><ph conref="refconrefs.dita#pub/citdevelop"></ph></cite>.</p></section>
 </refbody>
 </reference>
 

Modified: db/derby/docs/trunk/src/ref/rrefsqlj41180.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefsqlj41180.dita?view=diff&rev=487088&r1=487087&r2=487088
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefsqlj41180.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefsqlj41180.dita Wed Dec 13 23:49:30 2006
@@ -19,18 +19,26 @@
 <!DOCTYPE reference PUBLIC "-//OASIS//DTD DITA Reference//EN"
  "../dtd/reference.dtd">
 <reference id="rrefsqlj41180" xml:lang="en-us">
-<title>SET CURRENT ISOLATION statement</title>
+<title>SET ISOLATION statement</title>
 <prolog><metadata>
 <keywords><indexterm>SET ISOLATION statement</indexterm><indexterm>ISOLATION</indexterm>
 </keywords>
 </metadata></prolog>
 <refbody>
-<section> <p>The SET CURRENT ISOLATION LEVEL statement allows a user to change
+<section> <p>The SET ISOLATION statement allows a user to change
 the isolation level for the user's connection. Valid levels are SERIALIZABLE,
 REPEATABLE READ, READ COMMITTED, and READ UNCOMMITTED.</p> <p>Issuing this
-command commits the current transaction, which is consistent with the <i>java.sql.Connection.setTransactionLevel</i> method.</p> <p>For
-information about isolation levels, see "Locking, Concurrency, and Isolation"
-in the <cite><ph conref="refconrefs.dita#pub/citdevelop"></ph></cite>.</p></section>
+statement always commits the current transaction. The JDBC 
+<i>java.sql.Connection.setTransactionIsolation</i> method behaves almost 
+identically to this command, with one exception: if you are using the embedded 
+driver, and if the call to <i>java.sql.Connection.setTransactionIsolation</i>
+does not actually change the isolation level (that is, if it sets the isolation 
+level to its current value), the current transaction is not committed.</p> 
+<p>For information about isolation levels, see "Locking, concurrency, and 
+isolation"
+in the <cite><ph conref="refconrefs.dita#pub/citdevelop"></ph></cite>. For 
+information about the JDBC <i>java.sql.Connection.setTransactionIsolation</i> 
+method, see <xref href="rrefjavcsti.dita#rrefjavcsti"></xref>.</p></section>
 <refsyn><title>Syntax</title> <codeblock><b>SET [ CURRENT ] ISOLATION [ = ]
 {
 UR | DIRTY READ | READ UNCOMMITTED