db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From j..@apache.org
Subject svn commit: r159548 [4/17] - in incubator/derby/docs/trunk/src: adminguide/ devguide/ getstart/ tuning/
Date Thu, 31 Mar 2005 00:27:28 GMT
Modified: incubator/derby/docs/trunk/src/devguide/cdevconcepts15366.dita
URL: http://svn.apache.org/viewcvs/incubator/derby/docs/trunk/src/devguide/cdevconcepts15366.dita?view=diff&r1=159547&r2=159548
==============================================================================
--- incubator/derby/docs/trunk/src/devguide/cdevconcepts15366.dita (original)
+++ incubator/derby/docs/trunk/src/devguide/cdevconcepts15366.dita Wed Mar 30 16:26:36 2005
@@ -1,213 +1,213 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!-- 
-Copyright 1997, 2004 The Apache Software Foundation or its licensors, as applicable.  
-
-Licensed under the Apache License, Version 2.0 (the "License");  
-you may not use this file except in compliance with the License.  
-You may obtain a copy of the License at      
-
-   http://www.apache.org/licenses/LICENSE-2.0  
-
-Unless required by applicable law or agreed to in writing, software  
-distributed under the License is distributed on an "AS IS" BASIS,  
-WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.  
-See the License for the specific language governing permissions and  
-limitations under the License.
--->
-
-<!DOCTYPE concept PUBLIC "-//IBM//DTD DITA Concept//EN"
- "../dtd/concept.dtd">
-<concept id="cdevconcepts15366" xml:lang="en-us">
-<title>Isolation levels and concurrency</title>
-<prolog><metadata>
-<keywords><indexterm>Transaction anomalies in generic database systems<indexterm>description</indexterm></indexterm>
-<indexterm>java.sql.Connection.TRANSACTION_READ_UNCOMMITTED</indexterm><indexterm>java.sql.Connection.TRANSACTION_READ_COMMITTED</indexterm>
-<indexterm>java.sql.Connection.<?Pub Caret?>TRANSACTION_READ_COMMITTED</indexterm>
-<indexterm>java.sql.Connection.TRANSACTION_SERIALIZABLE</indexterm><indexterm>Dirty
-reads<indexterm>definition</indexterm></indexterm><indexterm>Non-repeatable
-reads<indexterm>definition</indexterm></indexterm><indexterm>Phantom reads<indexterm>definition</indexterm></indexterm>
-<indexterm>TRANSACTION_SERIALIZABLE isolation level</indexterm><indexterm>TRANSACTION_REPEATABLE_READ
-isolation level</indexterm><indexterm>TRANSACTION_READ_COMMITTED isolation
-level</indexterm><indexterm>TRANSACTION_READ_UNCOMMITTED isolation level</indexterm>
-</keywords>
-</metadata></prolog>
-<conbody>
-<p><ph conref="devconrefs.dita#prod/productshortname"></ph> provides four
-transaction isolation levels. Setting the transaction isolation level for
-a connection allows a user to specify how severely the user's transaction
-should be isolated from other transactions. For example, it allows you to
-specify whether transaction A is allowed to make changes to data that have
-been viewed by transaction B before transaction B has committed.</p>
-<p>A connection determines its own isolation level, so JDBC provides an application
-with a way to specify a level of transaction isolation. It specifies four
-levels of transaction isolation. The higher the transaction isolation, the
-more care is taken to avoid conflicts; avoiding conflicts sometimes means
-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
-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
-an SQL statement.</p>
-<table frame="all" id="cdevconceptsiso_level"><title>Mapping of JDBC transaction
-isolation levels to <ph conref="devconrefs.dita#prod/productshortname"></ph> isolation
-levels</title>
-<tgroup cols="2" colsep="1" rowsep="1"><colspec colname="colspec0" colwidth="260*"/>
-<colspec colname="colspec1" colwidth="186*"/>
-<thead>
-<row>
-<entry align="left" valign="top">Isolation levels for JDBC</entry>
-<entry align="left" valign="top">Isolation levels for SQL</entry>
-</row>
-</thead>
-<tbody>
-<row>
-<entry colname="colspec0">Connection.TRANSACTION_READ_ UNCOMMITTED (ANSI level
-0)</entry>
-<entry colname="colspec1">UR, DIRTY READ, READ UNCOMMITTED </entry>
-</row>
-<row>
-<entry colname="colspec0">Connection.TRANSACTION_READ_COMMITTED (ANSI level
-1) </entry>
-<entry colname="colspec1">CS, CURSOR STABILITY, READ COMMITTED</entry>
-</row>
-<row>
-<entry colname="colspec0">Connection.TRANSACTION_REPEATABLE_READ (ANSI level
-2) </entry>
-<entry colname="colspec1">RS</entry>
-</row>
-<row>
-<entry colname="colspec0">Connection.TRANSACTION_SERIALIZABLE (ANSI level
-3) </entry>
-<entry colname="colspec1">RR, REPEATABLE READ, SERIALIZABLE </entry>
-</row>
-</tbody>
-</tgroup>
-</table>
-<p>These levels allow you to avoid particular kinds of transaction anomalies,
-which are described in <xref href="#cdevconcepts15366/cdevconcepts17741"></xref>.</p>
-<table frame="all" id="cdevconcepts17741"><title>Transaction Anomalies</title>
-<tgroup cols="2" colsep="1" rowsep="1"><colspec colname="1" colnum="1" colwidth="48*"/>
-<colspec colname="2" colnum="2" colwidth="51*"/>
-<thead>
-<row>
-<entry colname="1">Anomaly</entry>
-<entry align="left" colname="2" valign="bottom">Example</entry>
-</row>
-</thead>
-<tbody>
-<row>
-<entry colname="1">Dirty Reads <p>A dirty read happens when a transaction
-reads data that is being modified by another transaction that has not yet
-committed.</p></entry>
-<entry colname="2">Transaction A begins.   <codeblock>UPDATE employee SET salary = 31650
-WHERE empno = '000090'</codeblock> Transaction B begins.   <codeblock>SELECT * FROM employee</codeblock> (Transaction
-B sees data updated by transaction A. Those updates have not yet been committed.)</entry>
-</row>
-<row>
-<entry colname="1">Non-Repeatable Reads <p>Non-repeatable reads happen when
-a query returns data that would be different if the query were repeated within
-the same transaction. Non-repeatable reads can occur when other transactions
-are modifying data that a transaction is reading.</p></entry>
-<entry colname="2">Transaction A begins.   <codeblock>SELECT * FROM employee
-WHERE empno = '000090' </codeblock> Transaction B begins.   <codeblock>UPDATE employee SET salary = 30100
-WHERE empno = '000090'</codeblock> (Transaction B updates rows viewed by transaction
-A before transaction A commits.) If Transaction A issues the same SELECT statement,
-the results will be different.</entry>
-</row>
-<row>
-<entry colname="1">Phantom Reads <p>Records that appear in a set being read
-by another transaction. Phantom reads can occur when other transactions insert
-rows that would satisfy the WHERE clause of another transaction's statement.</p></entry>
-<entry colname="2">Transaction A begins.   <codeblock>SELECT * FROM employee
- WHERE salary &gt; 30000 </codeblock> Transaction B begins.  <codeblock>INSERT INTO employee
-(empno, firstnme, midinit,
-lastname, job,
-salary) VALUES ('000350', 'NICK',
-'A','GREEN','LEGAL COUNSEL',35000)</codeblock> Transaction B inserts a row
-that would satisfy the query in Transaction A if it were issued again.</entry>
-</row>
-</tbody>
-</tgroup>
-</table>
-<p>The transaction isolation level is a way of specifying whether these transaction
-anomalies are allowed. The transaction isolation level thus affects the quantity
-of data locked by a particular transaction. In addition, a DBMS's locking
-schema might also affect whether these anomalies are allowed. A DBMS can lock
-either the entire table or only specific rows in order to prevent transaction
-anomalies.</p>
-<p><xref href="#cdevconcepts15366/cdevconcepts28076"></xref> shows which anomalies
-are possible under the various locking schemas and isolation levels.</p>
-<table frame="all" id="cdevconcepts28076"><title>When Transaction Anomalies
-Are Possible</title>
-<tgroup cols="3" colsep="1" rowsep="1"><colspec colname="1" colnum="1" colwidth="55*"/>
-<colspec colname="2" colnum="2" colwidth="20*"/><colspec colname="3" colnum="3"
-colwidth="21*"/>
-<thead>
-<row>
-<entry align="left" colname="1" valign="bottom">Isolation Level</entry>
-<entry align="left" colname="2" valign="bottom">Table-Level Locking</entry>
-<entry align="left" colname="3" valign="bottom">Row-Level Locking</entry>
-</row>
-</thead>
-<tbody>
-<row>
-<entry colname="1">TRANSACTION_READ_UNCOMMITTED</entry>
-<entry colname="2">Dirty reads, nonrepeatable reads, and phantom reads possible</entry>
-<entry colname="3">Dirty reads, nonrepeatable reads, and phantom reads possible</entry>
-</row>
-<row>
-<entry colname="1">TRANSACTION_READ_COMMITTED</entry>
-<entry colname="2">Nonrepeatable reads and phantom reads possible</entry>
-<entry colname="3">Nonrepeatable reads and phantom reads possible</entry>
-</row>
-<row>
-<entry colname="1">TRANSACTION_REPEATABLE_READ</entry>
-<entry colname="2">Phantom reads not possible because entire table is locked</entry>
-<entry colname="3">Phantom reads possible</entry>
-</row>
-<row>
-<entry colname="1">TRANSACTION_SERIALIZABLE</entry>
-<entry colname="2">None</entry>
-<entry colname="3">None</entry>
-</row>
-</tbody>
-</tgroup>
-</table>
-<p>The following <i>java.sql.Connection</i> isolation levels are supported:</p>
-<ul>
-<li><codeph>TRANSACTION_SERIALIZABLE</codeph> <p><codeph>RR</codeph>, <codeph>SERIALIZABLE</codeph>,
-or <codeph>REPEATABLE READ</codeph> from SQL.</p> <p><i>TRANSACTION_SERIALIZABLE</i> means
-that <ph conref="devconrefs.dita#prod/productshortname"></ph> treats the transactions
-as if they occurred serially (one after the other) instead of concurrently. <ph
-conref="devconrefs.dita#prod/productshortname"></ph> issues locks to prevent
-all the transaction anomalies listed in <xref href="#cdevconcepts15366/cdevconcepts17741"></xref> from
-occurring. The type of lock it issues is sometimes called a <i>range lock</i>.
-For more information about range locks, see <xref href="rdevconcepts8424.dita#rdevconcepts8424"></xref>.</p></li>
-<li><codeph>TRANSACTION_REPEATABLE_READ</codeph>   <p><codeph>RS</codeph> from
-SQL.</p> <p><i>TRANSACTION_REPEATABLE_READ</i> means that <ph conref="devconrefs.dita#prod/productshortname"></ph> issues
-locks to prevent only dirty reads and non-repeatable reads, but not phantoms.
-It does not issue range locks for selects.</p></li>
-<li><codeph>TRANSACTION_READ_COMMITTED</codeph>  <p><codeph>CS</codeph> or <codeph>CURSOR
-STABILITY</codeph> from SQL.</p> <p><i>TRANSACTION_READ_COMMITTED</i> means
-that <ph conref="devconrefs.dita#prod/productshortname"></ph> issues locks
-to prevent only dirty reads, not all the transaction anomalies listed in <xref
-href="#cdevconcepts15366/cdevconcepts17741"></xref>.</p> <p><i>TRANSACTION_READ_COMMITTED</i> is
-the default isolation level for transactions.</p></li>
-<li><codeph>TRANSACTION_READ_UNCOMMITTED</codeph>   <p><codeph>UR</codeph>, <codeph>DIRTY
-READ</codeph>, or <codeph>READ UNCOMMITTED</codeph> from SQL.</p> <p>For a
-SELECT INTO, FETCH with a read-only cursor, full select used in an INSERT,
-full select/subquery in an UPDATE/DELETE, or scalar full select (wherever
-used), READ UNCOMMITTED allows:</p> <ul>
-<li>Any row that is read during the unit of work to be changed by other application
-processes.</li>
-<li>Any row that was changed by another application process to be read even
-if the change has not been committed by the application process.</li>
-</ul> <p>For other operations, the rules that apply to READ COMMITTED also
-apply to READ UNCOMMITTED.</p></li>
-</ul>
-</conbody>
-</concept>
-<?Pub *0000010449?>
+<?xml version="1.0" encoding="utf-8"?>
+<!-- 
+Copyright 1997, 2004 The Apache Software Foundation or its licensors, as applicable.  
+
+Licensed under the Apache License, Version 2.0 (the "License");  
+you may not use this file except in compliance with the License.  
+You may obtain a copy of the License at      
+
+   http://www.apache.org/licenses/LICENSE-2.0  
+
+Unless required by applicable law or agreed to in writing, software  
+distributed under the License is distributed on an "AS IS" BASIS,  
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.  
+See the License for the specific language governing permissions and  
+limitations under the License.
+-->
+
+<!DOCTYPE concept PUBLIC "-//IBM//DTD DITA Concept//EN"
+ "../dtd/concept.dtd">
+<concept id="cdevconcepts15366" xml:lang="en-us">
+<title>Isolation levels and concurrency</title>
+<prolog><metadata>
+<keywords><indexterm>Transaction anomalies in generic database systems<indexterm>description</indexterm></indexterm>
+<indexterm>java.sql.Connection.TRANSACTION_READ_UNCOMMITTED</indexterm><indexterm>java.sql.Connection.TRANSACTION_READ_COMMITTED</indexterm>
+<indexterm>java.sql.Connection.<?Pub Caret?>TRANSACTION_READ_COMMITTED</indexterm>
+<indexterm>java.sql.Connection.TRANSACTION_SERIALIZABLE</indexterm><indexterm>Dirty
+reads<indexterm>definition</indexterm></indexterm><indexterm>Non-repeatable
+reads<indexterm>definition</indexterm></indexterm><indexterm>Phantom reads<indexterm>definition</indexterm></indexterm>
+<indexterm>TRANSACTION_SERIALIZABLE isolation level</indexterm><indexterm>TRANSACTION_REPEATABLE_READ
+isolation level</indexterm><indexterm>TRANSACTION_READ_COMMITTED isolation
+level</indexterm><indexterm>TRANSACTION_READ_UNCOMMITTED isolation level</indexterm>
+</keywords>
+</metadata></prolog>
+<conbody>
+<p><ph conref="devconrefs.dita#prod/productshortname"></ph> provides four
+transaction isolation levels. Setting the transaction isolation level for
+a connection allows a user to specify how severely the user's transaction
+should be isolated from other transactions. For example, it allows you to
+specify whether transaction A is allowed to make changes to data that have
+been viewed by transaction B before transaction B has committed.</p>
+<p>A connection determines its own isolation level, so JDBC provides an application
+with a way to specify a level of transaction isolation. It specifies four
+levels of transaction isolation. The higher the transaction isolation, the
+more care is taken to avoid conflicts; avoiding conflicts sometimes means
+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
+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
+an SQL statement.</p>
+<table frame="all" id="cdevconceptsiso_level"><title>Mapping of JDBC transaction
+isolation levels to <ph conref="devconrefs.dita#prod/productshortname"></ph> isolation
+levels</title>
+<tgroup cols="2" colsep="1" rowsep="1"><colspec colname="colspec0" colwidth="260*"/>
+<colspec colname="colspec1" colwidth="186*"/>
+<thead>
+<row>
+<entry align="left" valign="top">Isolation levels for JDBC</entry>
+<entry align="left" valign="top">Isolation levels for SQL</entry>
+</row>
+</thead>
+<tbody>
+<row>
+<entry colname="colspec0">Connection.TRANSACTION_READ_ UNCOMMITTED (ANSI level
+0)</entry>
+<entry colname="colspec1">UR, DIRTY READ, READ UNCOMMITTED </entry>
+</row>
+<row>
+<entry colname="colspec0">Connection.TRANSACTION_READ_COMMITTED (ANSI level
+1) </entry>
+<entry colname="colspec1">CS, CURSOR STABILITY, READ COMMITTED</entry>
+</row>
+<row>
+<entry colname="colspec0">Connection.TRANSACTION_REPEATABLE_READ (ANSI level
+2) </entry>
+<entry colname="colspec1">RS</entry>
+</row>
+<row>
+<entry colname="colspec0">Connection.TRANSACTION_SERIALIZABLE (ANSI level
+3) </entry>
+<entry colname="colspec1">RR, REPEATABLE READ, SERIALIZABLE </entry>
+</row>
+</tbody>
+</tgroup>
+</table>
+<p>These levels allow you to avoid particular kinds of transaction anomalies,
+which are described in <xref href="#cdevconcepts15366/cdevconcepts17741"></xref>.</p>
+<table frame="all" id="cdevconcepts17741"><title>Transaction Anomalies</title>
+<tgroup cols="2" colsep="1" rowsep="1"><colspec colname="1" colnum="1" colwidth="48*"/>
+<colspec colname="2" colnum="2" colwidth="51*"/>
+<thead>
+<row>
+<entry colname="1">Anomaly</entry>
+<entry align="left" colname="2" valign="bottom">Example</entry>
+</row>
+</thead>
+<tbody>
+<row>
+<entry colname="1">Dirty Reads <p>A dirty read happens when a transaction
+reads data that is being modified by another transaction that has not yet
+committed.</p></entry>
+<entry colname="2">Transaction A begins.   <codeblock>UPDATE employee SET salary = 31650
+WHERE empno = '000090'</codeblock> Transaction B begins.   <codeblock>SELECT * FROM employee</codeblock> (Transaction
+B sees data updated by transaction A. Those updates have not yet been committed.)</entry>
+</row>
+<row>
+<entry colname="1">Non-Repeatable Reads <p>Non-repeatable reads happen when
+a query returns data that would be different if the query were repeated within
+the same transaction. Non-repeatable reads can occur when other transactions
+are modifying data that a transaction is reading.</p></entry>
+<entry colname="2">Transaction A begins.   <codeblock>SELECT * FROM employee
+WHERE empno = '000090' </codeblock> Transaction B begins.   <codeblock>UPDATE employee SET salary = 30100
+WHERE empno = '000090'</codeblock> (Transaction B updates rows viewed by transaction
+A before transaction A commits.) If Transaction A issues the same SELECT statement,
+the results will be different.</entry>
+</row>
+<row>
+<entry colname="1">Phantom Reads <p>Records that appear in a set being read
+by another transaction. Phantom reads can occur when other transactions insert
+rows that would satisfy the WHERE clause of another transaction's statement.</p></entry>
+<entry colname="2">Transaction A begins.   <codeblock>SELECT * FROM employee
+ WHERE salary &gt; 30000 </codeblock> Transaction B begins.  <codeblock>INSERT INTO employee
+(empno, firstnme, midinit,
+lastname, job,
+salary) VALUES ('000350', 'NICK',
+'A','GREEN','LEGAL COUNSEL',35000)</codeblock> Transaction B inserts a row
+that would satisfy the query in Transaction A if it were issued again.</entry>
+</row>
+</tbody>
+</tgroup>
+</table>
+<p>The transaction isolation level is a way of specifying whether these transaction
+anomalies are allowed. The transaction isolation level thus affects the quantity
+of data locked by a particular transaction. In addition, a DBMS's locking
+schema might also affect whether these anomalies are allowed. A DBMS can lock
+either the entire table or only specific rows in order to prevent transaction
+anomalies.</p>
+<p><xref href="#cdevconcepts15366/cdevconcepts28076"></xref> shows which anomalies
+are possible under the various locking schemas and isolation levels.</p>
+<table frame="all" id="cdevconcepts28076"><title>When Transaction Anomalies
+Are Possible</title>
+<tgroup cols="3" colsep="1" rowsep="1"><colspec colname="1" colnum="1" colwidth="55*"/>
+<colspec colname="2" colnum="2" colwidth="20*"/><colspec colname="3" colnum="3"
+colwidth="21*"/>
+<thead>
+<row>
+<entry align="left" colname="1" valign="bottom">Isolation Level</entry>
+<entry align="left" colname="2" valign="bottom">Table-Level Locking</entry>
+<entry align="left" colname="3" valign="bottom">Row-Level Locking</entry>
+</row>
+</thead>
+<tbody>
+<row>
+<entry colname="1">TRANSACTION_READ_UNCOMMITTED</entry>
+<entry colname="2">Dirty reads, nonrepeatable reads, and phantom reads possible</entry>
+<entry colname="3">Dirty reads, nonrepeatable reads, and phantom reads possible</entry>
+</row>
+<row>
+<entry colname="1">TRANSACTION_READ_COMMITTED</entry>
+<entry colname="2">Nonrepeatable reads and phantom reads possible</entry>
+<entry colname="3">Nonrepeatable reads and phantom reads possible</entry>
+</row>
+<row>
+<entry colname="1">TRANSACTION_REPEATABLE_READ</entry>
+<entry colname="2">Phantom reads not possible because entire table is locked</entry>
+<entry colname="3">Phantom reads possible</entry>
+</row>
+<row>
+<entry colname="1">TRANSACTION_SERIALIZABLE</entry>
+<entry colname="2">None</entry>
+<entry colname="3">None</entry>
+</row>
+</tbody>
+</tgroup>
+</table>
+<p>The following <i>java.sql.Connection</i> isolation levels are supported:</p>
+<ul>
+<li><codeph>TRANSACTION_SERIALIZABLE</codeph> <p><codeph>RR</codeph>, <codeph>SERIALIZABLE</codeph>,
+or <codeph>REPEATABLE READ</codeph> from SQL.</p> <p><i>TRANSACTION_SERIALIZABLE</i> means
+that <ph conref="devconrefs.dita#prod/productshortname"></ph> treats the transactions
+as if they occurred serially (one after the other) instead of concurrently. <ph
+conref="devconrefs.dita#prod/productshortname"></ph> issues locks to prevent
+all the transaction anomalies listed in <xref href="#cdevconcepts15366/cdevconcepts17741"></xref> from
+occurring. The type of lock it issues is sometimes called a <i>range lock</i>.
+For more information about range locks, see <xref href="rdevconcepts8424.dita#rdevconcepts8424"></xref>.</p></li>
+<li><codeph>TRANSACTION_REPEATABLE_READ</codeph>   <p><codeph>RS</codeph> from
+SQL.</p> <p><i>TRANSACTION_REPEATABLE_READ</i> means that <ph conref="devconrefs.dita#prod/productshortname"></ph> issues
+locks to prevent only dirty reads and non-repeatable reads, but not phantoms.
+It does not issue range locks for selects.</p></li>
+<li><codeph>TRANSACTION_READ_COMMITTED</codeph>  <p><codeph>CS</codeph> or <codeph>CURSOR
+STABILITY</codeph> from SQL.</p> <p><i>TRANSACTION_READ_COMMITTED</i> means
+that <ph conref="devconrefs.dita#prod/productshortname"></ph> issues locks
+to prevent only dirty reads, not all the transaction anomalies listed in <xref
+href="#cdevconcepts15366/cdevconcepts17741"></xref>.</p> <p><i>TRANSACTION_READ_COMMITTED</i> is
+the default isolation level for transactions.</p></li>
+<li><codeph>TRANSACTION_READ_UNCOMMITTED</codeph>   <p><codeph>UR</codeph>, <codeph>DIRTY
+READ</codeph>, or <codeph>READ UNCOMMITTED</codeph> from SQL.</p> <p>For a
+SELECT INTO, FETCH with a read-only cursor, full select used in an INSERT,
+full select/subquery in an UPDATE/DELETE, or scalar full select (wherever
+used), READ UNCOMMITTED allows:</p> <ul>
+<li>Any row that is read during the unit of work to be changed by other application
+processes.</li>
+<li>Any row that was changed by another application process to be read even
+if the change has not been committed by the application process.</li>
+</ul> <p>For other operations, the rules that apply to READ COMMITTED also
+apply to READ UNCOMMITTED.</p></li>
+</ul>
+</conbody>
+</concept>
+<?Pub *0000010449?>

Propchange: incubator/derby/docs/trunk/src/devguide/cdevconcepts15366.dita
------------------------------------------------------------------------------
    svn:eol-style = native

Modified: incubator/derby/docs/trunk/src/devguide/cdevconcepts16400.dita
URL: http://svn.apache.org/viewcvs/incubator/derby/docs/trunk/src/devguide/cdevconcepts16400.dita?view=diff&r1=159547&r2=159548
==============================================================================
--- incubator/derby/docs/trunk/src/devguide/cdevconcepts16400.dita (original)
+++ incubator/derby/docs/trunk/src/devguide/cdevconcepts16400.dita Wed Mar 30 16:26:36 2005
@@ -1,46 +1,46 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!-- 
-Copyright 1997, 2004 The Apache Software Foundation or its licensors, as applicable.  
-
-Licensed under the Apache License, Version 2.0 (the "License");  
-you may not use this file except in compliance with the License.  
-You may obtain a copy of the License at      
-
-   http://www.apache.org/licenses/LICENSE-2.0  
-
-Unless required by applicable law or agreed to in writing, software  
-distributed under the License is distributed on an "AS IS" BASIS,  
-WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.  
-See the License for the specific language governing permissions and  
-limitations under the License.
--->
-<!DOCTYPE concept PUBLIC "-//IBM//DTD DITA Concept//EN" "../dtd/concept.dtd">
-<concept xml:lang="en-us" id="cdevconcepts16400">
-<title>Configuring deadlock detection and lock wait timeouts</title>
-<prolog>
-</prolog>
-<conbody>
-<p>You configure the amount of time a transaction waits before <ph conref="devconrefs.dita#prod/productshortname"></ph> does
-any deadlock checking with the <i>derby.locks.deadlockTimeout</i> property. You configure the amount of time a transaction waits before
-timing out with the <codeph><i>derby.locks.waitTimeout</i></codeph> property.
-When configuring your database or system, you should consider these properties
-together. For example, in order for any deadlock checking to occur, the <codeph><i>derby.locks.deadlockTimeout</i></codeph> property must be set
-to a value lower than the <codeph><i>derby.locks.waitTimeout</i></codeph> property. If it is set to a value equal to or higher than the <codeph><i>derby.locks.waitTimeout</i></codeph>, the transaction times out
-before <ph conref="devconrefs.dita#prod/productshortname"></ph> does any deadlock checking.</p>
-<p><indexterm>Deadlocks<indexterm>detecting</indexterm></indexterm>By
-default, <i>derby.locks.waitTimeout</i> is set to 60 seconds.
--1 is the equivalent of no wait timeout. This means that transactions never
-time out, although <ph conref="devconrefs.dita#prod/productshortname"></ph> can choose a transaction as a deadlock victim.</p>
-<fig id="cdevconcepts27089" expanse="column">
-<title>One possible configuration: deadlock
-checking occurs when a transaction has waited 30 seconds; no lock wait timeouts
-occur.</title><image placement="break" href="lockwa3.gif"><alt>This illustration depicts one possible configuration: deadlock checking occurs when a transaction has waited 30 seconds; no lock wait timeouts occur.</alt></image></fig>
-<fig id="cdevconcepts91443" expanse="column">
-<title>Another typical configuration:
-deadlock checking occurs after a transaction has waited 60 seconds for a lock;
-after 90 seconds, the transaction times out and is rolled back. </title><image placement="break" href="lockwa1.gif"><alt>This illustration depicts another typical configuration: deadlock checking occurs after a transaction has waited 60 seconds for a lock; after 90 seconds, the transaction times out and is rolled back.</alt></image></fig>
-<fig id="cdevconcepts14875" expanse="column">
-<title>A configuration in which no deadlock
-checking occurs: transactions time out after they have waited 50 seconds.
-No deadlock checking occurs. </title><image placement="break" href="lockwa2.gif"><alt>This illustration depicts a configuration in which no deadlock checking occurs: transactions time out after they have waited 50 seconds. No deadlock checking occurs.</alt></image></fig>
-</conbody></concept>
+<?xml version="1.0" encoding="utf-8"?>
+<!-- 
+Copyright 1997, 2004 The Apache Software Foundation or its licensors, as applicable.  
+
+Licensed under the Apache License, Version 2.0 (the "License");  
+you may not use this file except in compliance with the License.  
+You may obtain a copy of the License at      
+
+   http://www.apache.org/licenses/LICENSE-2.0  
+
+Unless required by applicable law or agreed to in writing, software  
+distributed under the License is distributed on an "AS IS" BASIS,  
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.  
+See the License for the specific language governing permissions and  
+limitations under the License.
+-->
+<!DOCTYPE concept PUBLIC "-//IBM//DTD DITA Concept//EN" "../dtd/concept.dtd">
+<concept xml:lang="en-us" id="cdevconcepts16400">
+<title>Configuring deadlock detection and lock wait timeouts</title>
+<prolog>
+</prolog>
+<conbody>
+<p>You configure the amount of time a transaction waits before <ph conref="devconrefs.dita#prod/productshortname"></ph> does
+any deadlock checking with the <i>derby.locks.deadlockTimeout</i> property. You configure the amount of time a transaction waits before
+timing out with the <codeph><i>derby.locks.waitTimeout</i></codeph> property.
+When configuring your database or system, you should consider these properties
+together. For example, in order for any deadlock checking to occur, the <codeph><i>derby.locks.deadlockTimeout</i></codeph> property must be set
+to a value lower than the <codeph><i>derby.locks.waitTimeout</i></codeph> property. If it is set to a value equal to or higher than the <codeph><i>derby.locks.waitTimeout</i></codeph>, the transaction times out
+before <ph conref="devconrefs.dita#prod/productshortname"></ph> does any deadlock checking.</p>
+<p><indexterm>Deadlocks<indexterm>detecting</indexterm></indexterm>By
+default, <i>derby.locks.waitTimeout</i> is set to 60 seconds.
+-1 is the equivalent of no wait timeout. This means that transactions never
+time out, although <ph conref="devconrefs.dita#prod/productshortname"></ph> can choose a transaction as a deadlock victim.</p>
+<fig id="cdevconcepts27089" expanse="column">
+<title>One possible configuration: deadlock
+checking occurs when a transaction has waited 30 seconds; no lock wait timeouts
+occur.</title><image placement="break" href="lockwa3.gif"><alt>This illustration depicts one possible configuration: deadlock checking occurs when a transaction has waited 30 seconds; no lock wait timeouts occur.</alt></image></fig>
+<fig id="cdevconcepts91443" expanse="column">
+<title>Another typical configuration:
+deadlock checking occurs after a transaction has waited 60 seconds for a lock;
+after 90 seconds, the transaction times out and is rolled back. </title><image placement="break" href="lockwa1.gif"><alt>This illustration depicts another typical configuration: deadlock checking occurs after a transaction has waited 60 seconds for a lock; after 90 seconds, the transaction times out and is rolled back.</alt></image></fig>
+<fig id="cdevconcepts14875" expanse="column">
+<title>A configuration in which no deadlock
+checking occurs: transactions time out after they have waited 50 seconds.
+No deadlock checking occurs. </title><image placement="break" href="lockwa2.gif"><alt>This illustration depicts a configuration in which no deadlock checking occurs: transactions time out after they have waited 50 seconds. No deadlock checking occurs.</alt></image></fig>
+</conbody></concept>

Propchange: incubator/derby/docs/trunk/src/devguide/cdevconcepts16400.dita
------------------------------------------------------------------------------
    svn:eol-style = native

Modified: incubator/derby/docs/trunk/src/devguide/cdevconcepts19173.dita
URL: http://svn.apache.org/viewcvs/incubator/derby/docs/trunk/src/devguide/cdevconcepts19173.dita?view=diff&r1=159547&r2=159548
==============================================================================
--- incubator/derby/docs/trunk/src/devguide/cdevconcepts19173.dita (original)
+++ incubator/derby/docs/trunk/src/devguide/cdevconcepts19173.dita Wed Mar 30 16:26:36 2005
@@ -1,39 +1,39 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!-- 
-Copyright 1997, 2004 The Apache Software Foundation or its licensors, as applicable.  
-
-Licensed under the Apache License, Version 2.0 (the "License");  
-you may not use this file except in compliance with the License.  
-You may obtain a copy of the License at      
-
-   http://www.apache.org/licenses/LICENSE-2.0  
-
-Unless required by applicable law or agreed to in writing, software  
-distributed under the License is distributed on an "AS IS" BASIS,  
-WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.  
-See the License for the specific language governing permissions and  
-limitations under the License.
--->
-<!DOCTYPE concept PUBLIC "-//IBM//DTD DITA Concept//EN" "../dtd/concept.dtd">
-<concept xml:lang="en-us" id="cdevconcepts19173">
-<title>Transactions</title>
-<prolog><metadata>
-<keywords>
-<indexterm>Transactions<indexterm>definition</indexterm></indexterm>
-</keywords>
-</metadata>
-</prolog>
-<conbody>
-<p>A <i>transaction</i> is a set of one or more SQL statements
-that make up a logical unit of work that you can either commit or roll back
-and that will be recovered in the event of a system failure. All the statements
-in the transaction are <i>atomic</i>. A transaction is associated
-with a single <codeph><i>Connection</i></codeph> object (and database).
-A transaction cannot span <i>Connections</i> (or databases).</p>
-<p><ph conref="devconrefs.dita#prod/productshortname"></ph> permits schema and data manipulation statements (DML) to be
-intermixed within a single transaction. If you create a table in one transaction,
-you can also insert into it in that same transaction. A schema manipulation
-statement (DDL) is not automatically committed when it is performed, but participates
-in the transaction within which it is issued. Because DDL requires exclusive
-locks on system tables, keep transactions that involve DDL short.</p>
-</conbody></concept>
+<?xml version="1.0" encoding="utf-8"?>
+<!-- 
+Copyright 1997, 2004 The Apache Software Foundation or its licensors, as applicable.  
+
+Licensed under the Apache License, Version 2.0 (the "License");  
+you may not use this file except in compliance with the License.  
+You may obtain a copy of the License at      
+
+   http://www.apache.org/licenses/LICENSE-2.0  
+
+Unless required by applicable law or agreed to in writing, software  
+distributed under the License is distributed on an "AS IS" BASIS,  
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.  
+See the License for the specific language governing permissions and  
+limitations under the License.
+-->
+<!DOCTYPE concept PUBLIC "-//IBM//DTD DITA Concept//EN" "../dtd/concept.dtd">
+<concept xml:lang="en-us" id="cdevconcepts19173">
+<title>Transactions</title>
+<prolog><metadata>
+<keywords>
+<indexterm>Transactions<indexterm>definition</indexterm></indexterm>
+</keywords>
+</metadata>
+</prolog>
+<conbody>
+<p>A <i>transaction</i> is a set of one or more SQL statements
+that make up a logical unit of work that you can either commit or roll back
+and that will be recovered in the event of a system failure. All the statements
+in the transaction are <i>atomic</i>. A transaction is associated
+with a single <codeph><i>Connection</i></codeph> object (and database).
+A transaction cannot span <i>Connections</i> (or databases).</p>
+<p><ph conref="devconrefs.dita#prod/productshortname"></ph> permits schema and data manipulation statements (DML) to be
+intermixed within a single transaction. If you create a table in one transaction,
+you can also insert into it in that same transaction. A schema manipulation
+statement (DDL) is not automatically committed when it is performed, but participates
+in the transaction within which it is issued. Because DDL requires exclusive
+locks on system tables, keep transactions that involve DDL short.</p>
+</conbody></concept>

Propchange: incubator/derby/docs/trunk/src/devguide/cdevconcepts19173.dita
------------------------------------------------------------------------------
    svn:eol-style = native

Modified: incubator/derby/docs/trunk/src/devguide/cdevconcepts19524.dita
URL: http://svn.apache.org/viewcvs/incubator/derby/docs/trunk/src/devguide/cdevconcepts19524.dita?view=diff&r1=159547&r2=159548
==============================================================================
--- incubator/derby/docs/trunk/src/devguide/cdevconcepts19524.dita (original)
+++ incubator/derby/docs/trunk/src/devguide/cdevconcepts19524.dita Wed Mar 30 16:26:36 2005
@@ -1,32 +1,32 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!-- 
-Copyright 1997, 2004 The Apache Software Foundation or its licensors, as applicable.  
-
-Licensed under the Apache License, Version 2.0 (the "License");  
-you may not use this file except in compliance with the License.  
-You may obtain a copy of the License at      
-
-   http://www.apache.org/licenses/LICENSE-2.0  
-
-Unless required by applicable law or agreed to in writing, software  
-distributed under the License is distributed on an "AS IS" BASIS,  
-WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.  
-See the License for the specific language governing permissions and  
-limitations under the License.
--->
-<!DOCTYPE concept PUBLIC "-//IBM//DTD DITA Concept//EN" "../dtd/concept.dtd">
-<concept xml:lang="en-us" id="cdevconcepts19524">
-<title>Controlling Derby Application Behavior</title>
-<prolog>
-</prolog>
-<conbody>
-<p>This chapter looks at some advanced <ph conref="devconrefs.dita#prod/productshortname"></ph> concepts:</p>
-<ul>
-<li><xref href="cdevconcepts38375.dita#cdevconcepts38375"/></li>
-<li><xref href="cdevconcepts41275.dita#cdevconcepts41275"/></li>
-<li><xref href="cdevconcepts30291.dita#cdevconcepts30291"/></li>
-<li><xref href="cdevconcepts34828.dita#cdevconcepts34828"/></li>
-<li><xref href="cdevconcepts23499.dita#cdevconcepts23499"/></li>
-<li><xref href="cdevconcepts24927.dita#cdevconcepts24927"/></li>
-</ul>
-</conbody></concept>
+<?xml version="1.0" encoding="utf-8"?>
+<!-- 
+Copyright 1997, 2004 The Apache Software Foundation or its licensors, as applicable.  
+
+Licensed under the Apache License, Version 2.0 (the "License");  
+you may not use this file except in compliance with the License.  
+You may obtain a copy of the License at      
+
+   http://www.apache.org/licenses/LICENSE-2.0  
+
+Unless required by applicable law or agreed to in writing, software  
+distributed under the License is distributed on an "AS IS" BASIS,  
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.  
+See the License for the specific language governing permissions and  
+limitations under the License.
+-->
+<!DOCTYPE concept PUBLIC "-//IBM//DTD DITA Concept//EN" "../dtd/concept.dtd">
+<concept xml:lang="en-us" id="cdevconcepts19524">
+<title>Controlling Derby Application Behavior</title>
+<prolog>
+</prolog>
+<conbody>
+<p>This chapter looks at some advanced <ph conref="devconrefs.dita#prod/productshortname"></ph> concepts:</p>
+<ul>
+<li><xref href="cdevconcepts38375.dita#cdevconcepts38375"/></li>
+<li><xref href="cdevconcepts41275.dita#cdevconcepts41275"/></li>
+<li><xref href="cdevconcepts30291.dita#cdevconcepts30291"/></li>
+<li><xref href="cdevconcepts34828.dita#cdevconcepts34828"/></li>
+<li><xref href="cdevconcepts23499.dita#cdevconcepts23499"/></li>
+<li><xref href="cdevconcepts24927.dita#cdevconcepts24927"/></li>
+</ul>
+</conbody></concept>

Propchange: incubator/derby/docs/trunk/src/devguide/cdevconcepts19524.dita
------------------------------------------------------------------------------
    svn:eol-style = native

Modified: incubator/derby/docs/trunk/src/devguide/cdevconcepts22300.dita
URL: http://svn.apache.org/viewcvs/incubator/derby/docs/trunk/src/devguide/cdevconcepts22300.dita?view=diff&r1=159547&r2=159548
==============================================================================
--- incubator/derby/docs/trunk/src/devguide/cdevconcepts22300.dita (original)
+++ incubator/derby/docs/trunk/src/devguide/cdevconcepts22300.dita Wed Mar 30 16:26:36 2005
@@ -1,45 +1,45 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!-- 
-Copyright 1997, 2004 The Apache Software Foundation or its licensors, as applicable.  
-
-Licensed under the Apache License, Version 2.0 (the "License");  
-you may not use this file except in compliance with the License.  
-You may obtain a copy of the License at      
-
-   http://www.apache.org/licenses/LICENSE-2.0  
-
-Unless required by applicable law or agreed to in writing, software  
-distributed under the License is distributed on an "AS IS" BASIS,  
-WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.  
-See the License for the specific language governing permissions and  
-limitations under the License.
--->
-<!DOCTYPE concept PUBLIC "-//IBM//DTD DITA Concept//EN" "../dtd/concept.dtd">
-<concept xml:lang="en-us" id="cdevconcepts22300">
-<title>Configuring isolation levels</title>
-<prolog><metadata>
-<keywords>
-<indexterm>Isolation levels<indexterm>configuring</indexterm></indexterm>
-</keywords>
-</metadata>
-</prolog>
-<conbody>
-<p>If a connection does not specify its isolation level, it inherits the default
-isolation level for the <ph conref="devconrefs.dita#prod/productshortname"></ph> system, The default value is <codeph>CS</codeph>.
-When set to <codeph>CS</codeph>, the connection inherits the TRANSACTION_READ_COMMITTED
-isolation level. When set to <codeph>RR</codeph>, the connection inherits the TRANSACTION_SERIALIZABLE
-isolation level, when set to <codeph>RS</codeph>, the connection inherits the TRANSACTION_REPEATABLE_READ
-isolation level, and when set to <codeph>UR</codeph>, the connection inherits the
-TRANSACTION_READ_UNCOMMITTED isolation level.</p>
-<p>To override the inherited default, use the methods of <i>java.sql.Connection</i>.</p>
-<p>In addition, a connection can change the isolation level of the transaction
-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>
-<p> In all cases except when you change the isolation level using the WITH
-clause, changing the isolation level commits the current transaction.</p>
-<note>For information about how to choose a particular isolation
-level, see <cite><ph conref="devconrefs.dita#pub/cittuning"></ph></cite>.</note>
-</conbody></concept>
+<?xml version="1.0" encoding="utf-8"?>
+<!-- 
+Copyright 1997, 2004 The Apache Software Foundation or its licensors, as applicable.  
+
+Licensed under the Apache License, Version 2.0 (the "License");  
+you may not use this file except in compliance with the License.  
+You may obtain a copy of the License at      
+
+   http://www.apache.org/licenses/LICENSE-2.0  
+
+Unless required by applicable law or agreed to in writing, software  
+distributed under the License is distributed on an "AS IS" BASIS,  
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.  
+See the License for the specific language governing permissions and  
+limitations under the License.
+-->
+<!DOCTYPE concept PUBLIC "-//IBM//DTD DITA Concept//EN" "../dtd/concept.dtd">
+<concept xml:lang="en-us" id="cdevconcepts22300">
+<title>Configuring isolation levels</title>
+<prolog><metadata>
+<keywords>
+<indexterm>Isolation levels<indexterm>configuring</indexterm></indexterm>
+</keywords>
+</metadata>
+</prolog>
+<conbody>
+<p>If a connection does not specify its isolation level, it inherits the default
+isolation level for the <ph conref="devconrefs.dita#prod/productshortname"></ph> system, The default value is <codeph>CS</codeph>.
+When set to <codeph>CS</codeph>, the connection inherits the TRANSACTION_READ_COMMITTED
+isolation level. When set to <codeph>RR</codeph>, the connection inherits the TRANSACTION_SERIALIZABLE
+isolation level, when set to <codeph>RS</codeph>, the connection inherits the TRANSACTION_REPEATABLE_READ
+isolation level, and when set to <codeph>UR</codeph>, the connection inherits the
+TRANSACTION_READ_UNCOMMITTED isolation level.</p>
+<p>To override the inherited default, use the methods of <i>java.sql.Connection</i>.</p>
+<p>In addition, a connection can change the isolation level of the transaction
+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>
+<p> In all cases except when you change the isolation level using the WITH
+clause, changing the isolation level commits the current transaction.</p>
+<note>For information about how to choose a particular isolation
+level, see <cite><ph conref="devconrefs.dita#pub/cittuning"></ph></cite>.</note>
+</conbody></concept>

Propchange: incubator/derby/docs/trunk/src/devguide/cdevconcepts22300.dita
------------------------------------------------------------------------------
    svn:eol-style = native

Modified: incubator/derby/docs/trunk/src/devguide/cdevconcepts22641.dita
URL: http://svn.apache.org/viewcvs/incubator/derby/docs/trunk/src/devguide/cdevconcepts22641.dita?view=diff&r1=159547&r2=159548
==============================================================================
--- incubator/derby/docs/trunk/src/devguide/cdevconcepts22641.dita (original)
+++ incubator/derby/docs/trunk/src/devguide/cdevconcepts22641.dita Wed Mar 30 16:26:36 2005
@@ -1,70 +1,70 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!-- 
-Copyright 1997, 2004 The Apache Software Foundation or its licensors, as applicable.  
-
-Licensed under the Apache License, Version 2.0 (the "License");  
-you may not use this file except in compliance with the License.  
-You may obtain a copy of the License at      
-
-   http://www.apache.org/licenses/LICENSE-2.0  
-
-Unless required by applicable law or agreed to in writing, software  
-distributed under the License is distributed on an "AS IS" BASIS,  
-WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.  
-See the License for the specific language governing permissions and  
-limitations under the License.
--->
-<!DOCTYPE concept PUBLIC "-//IBM//DTD DITA Concept//EN" "../dtd/concept.dtd">
-<concept xml:lang="en-us" id="cdevconcepts22641">
-<title>Scrolling insensitive ResultSets</title>
-<prolog><metadata>
-<keywords>
-<indexterm>Scrolling insensitive cursors</indexterm>
-<indexterm>ResultSets<indexterm>scrolling insensitive (JDBC
-2.0)</indexterm></indexterm>
-<indexterm>Cursors<indexterm>scrolling insensitive</indexterm></indexterm>
-</keywords>
-</metadata>
-</prolog>
-<conbody>
-<p>JDBC 2.0 adds a new kind of <codeph><i>ResultSet</i></codeph>,
-one that allows you to scroll in either direction or to move the cursor to
-a particular row. <ph conref="devconrefs.dita#prod/productshortname"></ph> implements scrolling insensitive <codeph><i>ResultSets</i></codeph>. When you use a scroll insensitive <codeph><i>ResultSets</i></codeph> cursor to facilitate the insensitive scrolling action,
-<ph conref="devconrefs.dita#prod/productshortname"></ph> materializes in memory all rows from the first one in the result set
-up to the one with the biggest row number.</p>
-<codeblock><b>//autocommit does not have to be off because even if 
-//we accidentally scroll past the last row, the implicit commit
-//on the the statement will not close the result set because result sets
-//are held over commit by default</b>
-conn.setAutoCommit(false);
-Statement s4 = conn.createStatement(
-ResultSet.TYPE_SCROLL_INSENSITIVE, ResultSet.CONCUR_READ_ONLY);
-s4.execute("set schema 'SAMP'");
-ResultSet scroller=s4.executeQuery(
-    "SELECT sales_person, region, sales FROM sales " +
-    "WHERE sales &gt; 8 ORDER BY sales DESC");
-if (scroller.first())
-    System.out.println("The sales rep who sold the highest number
-				of sales is " +
-           scroller.getString("SALES_PERSON"));
-else
-    System.out.println("There are no rows.");
-scroller.beforeFirst();
-scroller.afterLast();
-scroller.absolute(3);
-if (!scroller.isAfterLast()) 
-    System.out.println("The employee with the third highest number
-				of sales is " +
-           scroller.getString("SALES_PERSON") + ", with " +
-           scroller.getInt("SALES") + " sales");
-if (scroller.isLast())
-    System.out.println("There are only three rows.");
-if (scroller.last())
-    System.out.println("The least highest number
-				of sales of the top three sales is: " +
-           scroller.getInt("SALES"));
-scroller.close();
-s4.close();
-conn.close();
-System.out.println("Closed connection");</codeblock>
-</conbody></concept>
+<?xml version="1.0" encoding="utf-8"?>
+<!-- 
+Copyright 1997, 2004 The Apache Software Foundation or its licensors, as applicable.  
+
+Licensed under the Apache License, Version 2.0 (the "License");  
+you may not use this file except in compliance with the License.  
+You may obtain a copy of the License at      
+
+   http://www.apache.org/licenses/LICENSE-2.0  
+
+Unless required by applicable law or agreed to in writing, software  
+distributed under the License is distributed on an "AS IS" BASIS,  
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.  
+See the License for the specific language governing permissions and  
+limitations under the License.
+-->
+<!DOCTYPE concept PUBLIC "-//IBM//DTD DITA Concept//EN" "../dtd/concept.dtd">
+<concept xml:lang="en-us" id="cdevconcepts22641">
+<title>Scrolling insensitive ResultSets</title>
+<prolog><metadata>
+<keywords>
+<indexterm>Scrolling insensitive cursors</indexterm>
+<indexterm>ResultSets<indexterm>scrolling insensitive (JDBC
+2.0)</indexterm></indexterm>
+<indexterm>Cursors<indexterm>scrolling insensitive</indexterm></indexterm>
+</keywords>
+</metadata>
+</prolog>
+<conbody>
+<p>JDBC 2.0 adds a new kind of <codeph><i>ResultSet</i></codeph>,
+one that allows you to scroll in either direction or to move the cursor to
+a particular row. <ph conref="devconrefs.dita#prod/productshortname"></ph> implements scrolling insensitive <codeph><i>ResultSets</i></codeph>. When you use a scroll insensitive <codeph><i>ResultSets</i></codeph> cursor to facilitate the insensitive scrolling action,
+<ph conref="devconrefs.dita#prod/productshortname"></ph> materializes in memory all rows from the first one in the result set
+up to the one with the biggest row number.</p>
+<codeblock><b>//autocommit does not have to be off because even if 
+//we accidentally scroll past the last row, the implicit commit
+//on the the statement will not close the result set because result sets
+//are held over commit by default</b>
+conn.setAutoCommit(false);
+Statement s4 = conn.createStatement(
+ResultSet.TYPE_SCROLL_INSENSITIVE, ResultSet.CONCUR_READ_ONLY);
+s4.execute("set schema 'SAMP'");
+ResultSet scroller=s4.executeQuery(
+    "SELECT sales_person, region, sales FROM sales " +
+    "WHERE sales &gt; 8 ORDER BY sales DESC");
+if (scroller.first())
+    System.out.println("The sales rep who sold the highest number
+				of sales is " +
+           scroller.getString("SALES_PERSON"));
+else
+    System.out.println("There are no rows.");
+scroller.beforeFirst();
+scroller.afterLast();
+scroller.absolute(3);
+if (!scroller.isAfterLast()) 
+    System.out.println("The employee with the third highest number
+				of sales is " +
+           scroller.getString("SALES_PERSON") + ", with " +
+           scroller.getInt("SALES") + " sales");
+if (scroller.isLast())
+    System.out.println("There are only three rows.");
+if (scroller.last())
+    System.out.println("The least highest number
+				of sales of the top three sales is: " +
+           scroller.getInt("SALES"));
+scroller.close();
+s4.close();
+conn.close();
+System.out.println("Closed connection");</codeblock>
+</conbody></concept>

Propchange: incubator/derby/docs/trunk/src/devguide/cdevconcepts22641.dita
------------------------------------------------------------------------------
    svn:eol-style = native

Modified: incubator/derby/docs/trunk/src/devguide/cdevconcepts23499.dita
URL: http://svn.apache.org/viewcvs/incubator/derby/docs/trunk/src/devguide/cdevconcepts23499.dita?view=diff&r1=159547&r2=159548
==============================================================================
--- incubator/derby/docs/trunk/src/devguide/cdevconcepts23499.dita (original)
+++ incubator/derby/docs/trunk/src/devguide/cdevconcepts23499.dita Wed Mar 30 16:26:36 2005
@@ -1,34 +1,34 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!-- 
-Copyright 1997, 2004 The Apache Software Foundation or its licensors, as applicable.  
-
-Licensed under the Apache License, Version 2.0 (the "License");  
-you may not use this file except in compliance with the License.  
-You may obtain a copy of the License at      
-
-   http://www.apache.org/licenses/LICENSE-2.0  
-
-Unless required by applicable law or agreed to in writing, software  
-distributed under the License is distributed on an "AS IS" BASIS,  
-WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.  
-See the License for the specific language governing permissions and  
-limitations under the License.
--->
-<!DOCTYPE concept PUBLIC "-//IBM//DTD DITA Concept//EN" "../dtd/concept.dtd">
-<concept xml:lang="en-us" id="cdevconcepts23499">
-<title>Working with multiple threads sharing a single connection</title>
-<prolog><metadata>
-<keywords>
-<indexterm>Multiple threads sharing single connection</indexterm>
-</keywords>
-</metadata>
-</prolog>
-<conbody>
-<p>JDBC allows you to share a single <i>Connection</i> among
-multiple threads.</p>
-<ul>
-<li><xref href="cdevconcepts89498.dita#cdevconcepts89498"/></li>
-<li><xref href="cdevconcepts65864.dita#cdevconcepts65864"/></li>
-<li><xref href="rdevconcepts600.dita#rdevconcepts600"/></li>
-</ul>
-</conbody></concept>
+<?xml version="1.0" encoding="utf-8"?>
+<!-- 
+Copyright 1997, 2004 The Apache Software Foundation or its licensors, as applicable.  
+
+Licensed under the Apache License, Version 2.0 (the "License");  
+you may not use this file except in compliance with the License.  
+You may obtain a copy of the License at      
+
+   http://www.apache.org/licenses/LICENSE-2.0  
+
+Unless required by applicable law or agreed to in writing, software  
+distributed under the License is distributed on an "AS IS" BASIS,  
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.  
+See the License for the specific language governing permissions and  
+limitations under the License.
+-->
+<!DOCTYPE concept PUBLIC "-//IBM//DTD DITA Concept//EN" "../dtd/concept.dtd">
+<concept xml:lang="en-us" id="cdevconcepts23499">
+<title>Working with multiple threads sharing a single connection</title>
+<prolog><metadata>
+<keywords>
+<indexterm>Multiple threads sharing single connection</indexterm>
+</keywords>
+</metadata>
+</prolog>
+<conbody>
+<p>JDBC allows you to share a single <i>Connection</i> among
+multiple threads.</p>
+<ul>
+<li><xref href="cdevconcepts89498.dita#cdevconcepts89498"/></li>
+<li><xref href="cdevconcepts65864.dita#cdevconcepts65864"/></li>
+<li><xref href="rdevconcepts600.dita#rdevconcepts600"/></li>
+</ul>
+</conbody></concept>

Propchange: incubator/derby/docs/trunk/src/devguide/cdevconcepts23499.dita
------------------------------------------------------------------------------
    svn:eol-style = native

Modified: incubator/derby/docs/trunk/src/devguide/cdevconcepts23810.dita
URL: http://svn.apache.org/viewcvs/incubator/derby/docs/trunk/src/devguide/cdevconcepts23810.dita?view=diff&r1=159547&r2=159548
==============================================================================
--- incubator/derby/docs/trunk/src/devguide/cdevconcepts23810.dita (original)
+++ incubator/derby/docs/trunk/src/devguide/cdevconcepts23810.dita Wed Mar 30 16:26:36 2005
@@ -1,44 +1,44 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!-- 
-Copyright 1997, 2004 The Apache Software Foundation or its licensors, as applicable.  
-
-Licensed under the Apache License, Version 2.0 (the "License");  
-you may not use this file except in compliance with the License.  
-You may obtain a copy of the License at      
-
-   http://www.apache.org/licenses/LICENSE-2.0  
-
-Unless required by applicable law or agreed to in writing, software  
-distributed under the License is distributed on an "AS IS" BASIS,  
-WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.  
-See the License for the specific language governing permissions and  
-limitations under the License.
--->
-<!DOCTYPE concept PUBLIC "-//IBM//DTD DITA Concept//EN" "../dtd/concept.dtd">
-<concept xml:lang="en-us" id="cdevconcepts23810">
-<title>Lock granularity</title>
-<prolog><metadata>
-<keywords>
-<indexterm>Lock granularity</indexterm>
-<indexterm>Locking<indexterm>table-level</indexterm><indexterm>row-level</indexterm></indexterm>
-</keywords>
-</metadata>
-</prolog>
-<conbody>
-<p id="cdevconcepts18383"><ph conref="devconrefs.dita#prod/productshortname"></ph> can be configured for <i>table-level</i> locking. With table-level locking, when a transaction locks
-data in order to prevent any transaction anomalies, it always locks the entire
-table, not just those rows being accessed.</p>
-<p>By default, <ph conref="devconrefs.dita#prod/productshortname"></ph> is configured for row-level locking. Row-level
-locking uses more memory but allows greater concurrency, which works better
-in multi-user systems. Table-level locking works best with single-user applications
-or read-only applications. </p>
-<p>You typically set lock granularity for the entire <ph conref="devconrefs.dita#prod/productshortname"></ph> system, not
-for a particular application. However, at runtime, <ph conref="devconrefs.dita#prod/productshortname"></ph> may escalate
-the lock granularity for a particular transaction from row-level locking to
-table-level locking for performance reasons. You have some control over the
-threshold at which this occurs. For information on turning off row-level locking,
-see <i>"derby.storage.rowLocking" </i> in <cite><ph conref="devconrefs.dita#pub/cittuning"></ph></cite>. For more information about automatic lock escalation, see "About
-the System's Selection of Lock Granularity" and "Transaction-Based
-Lock Escalation" in <cite><ph conref="devconrefs.dita#pub/cittuning"></ph></cite><cite>. </cite>For more information
-on tuning your <ph conref="devconrefs.dita#prod/productshortname"></ph> system, see "Tuning Databases and Applications".</p>
-</conbody></concept>
+<?xml version="1.0" encoding="utf-8"?>
+<!-- 
+Copyright 1997, 2004 The Apache Software Foundation or its licensors, as applicable.  
+
+Licensed under the Apache License, Version 2.0 (the "License");  
+you may not use this file except in compliance with the License.  
+You may obtain a copy of the License at      
+
+   http://www.apache.org/licenses/LICENSE-2.0  
+
+Unless required by applicable law or agreed to in writing, software  
+distributed under the License is distributed on an "AS IS" BASIS,  
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.  
+See the License for the specific language governing permissions and  
+limitations under the License.
+-->
+<!DOCTYPE concept PUBLIC "-//IBM//DTD DITA Concept//EN" "../dtd/concept.dtd">
+<concept xml:lang="en-us" id="cdevconcepts23810">
+<title>Lock granularity</title>
+<prolog><metadata>
+<keywords>
+<indexterm>Lock granularity</indexterm>
+<indexterm>Locking<indexterm>table-level</indexterm><indexterm>row-level</indexterm></indexterm>
+</keywords>
+</metadata>
+</prolog>
+<conbody>
+<p id="cdevconcepts18383"><ph conref="devconrefs.dita#prod/productshortname"></ph> can be configured for <i>table-level</i> locking. With table-level locking, when a transaction locks
+data in order to prevent any transaction anomalies, it always locks the entire
+table, not just those rows being accessed.</p>
+<p>By default, <ph conref="devconrefs.dita#prod/productshortname"></ph> is configured for row-level locking. Row-level
+locking uses more memory but allows greater concurrency, which works better
+in multi-user systems. Table-level locking works best with single-user applications
+or read-only applications. </p>
+<p>You typically set lock granularity for the entire <ph conref="devconrefs.dita#prod/productshortname"></ph> system, not
+for a particular application. However, at runtime, <ph conref="devconrefs.dita#prod/productshortname"></ph> may escalate
+the lock granularity for a particular transaction from row-level locking to
+table-level locking for performance reasons. You have some control over the
+threshold at which this occurs. For information on turning off row-level locking,
+see <i>"derby.storage.rowLocking" </i> in <cite><ph conref="devconrefs.dita#pub/cittuning"></ph></cite>. For more information about automatic lock escalation, see "About
+the System's Selection of Lock Granularity" and "Transaction-Based
+Lock Escalation" in <cite><ph conref="devconrefs.dita#pub/cittuning"></ph></cite><cite>. </cite>For more information
+on tuning your <ph conref="devconrefs.dita#prod/productshortname"></ph> system, see "Tuning Databases and Applications".</p>
+</conbody></concept>

Propchange: incubator/derby/docs/trunk/src/devguide/cdevconcepts23810.dita
------------------------------------------------------------------------------
    svn:eol-style = native

Modified: incubator/derby/docs/trunk/src/devguide/cdevconcepts23987.dita
URL: http://svn.apache.org/viewcvs/incubator/derby/docs/trunk/src/devguide/cdevconcepts23987.dita?view=diff&r1=159547&r2=159548
==============================================================================
--- incubator/derby/docs/trunk/src/devguide/cdevconcepts23987.dita (original)
+++ incubator/derby/docs/trunk/src/devguide/cdevconcepts23987.dita Wed Mar 30 16:26:36 2005
@@ -1,35 +1,35 @@
-<?xml version="1.0" encoding="utf-8"?>
-
-<!DOCTYPE concept PUBLIC "-//IBM//DTD DITA Concept//EN"
- "../dtd/concept.dtd">
-<!-- 
-Copyright 1997, 2004 The Apache Software Foundation or its licensors, as applicable.  
-
-Licensed under the Apache License, Version 2.0 (the "License");  
-you may not use this file except in compliance with the License.  
-You may obtain a copy of the License at      
-
-   http://www.apache.org/licenses/LICENSE-2.0  
-
-Unless required by applicable law or agreed to in writing, software  
-distributed under the License is distributed on an "AS IS" BASIS,  
-WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.  
-See the License for the specific language governing permissions and  
-limitations under the License.
--->
-<concept id="cdevconcepts23987" xml:lang="en-us">
-<title>ResultSets and auto-commit</title>
-<prolog><metadata>
-<keywords><indexterm>ResultSets<indexterm>behavior of with auto-commit</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<conbody>
-<p>Except for the result sets associated with holdable cursors (see <xref
-href="rdevconceptsholdablecursors.dita#rdevconceptsholdablecursors"></xref> for
-more information), issuing a commit will cause all result sets on your connection
-to be closed.</p>
-<p>The JDBC program is not required to have auto-commit off when using updatable
-ResultSets.<?Pub Caret?></p>
-</conbody>
-</concept>
-<?Pub *0000001456?>
+<?xml version="1.0" encoding="utf-8"?>
+
+<!DOCTYPE concept PUBLIC "-//IBM//DTD DITA Concept//EN"
+ "../dtd/concept.dtd">
+<!-- 
+Copyright 1997, 2004 The Apache Software Foundation or its licensors, as applicable.  
+
+Licensed under the Apache License, Version 2.0 (the "License");  
+you may not use this file except in compliance with the License.  
+You may obtain a copy of the License at      
+
+   http://www.apache.org/licenses/LICENSE-2.0  
+
+Unless required by applicable law or agreed to in writing, software  
+distributed under the License is distributed on an "AS IS" BASIS,  
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.  
+See the License for the specific language governing permissions and  
+limitations under the License.
+-->
+<concept id="cdevconcepts23987" xml:lang="en-us">
+<title>ResultSets and auto-commit</title>
+<prolog><metadata>
+<keywords><indexterm>ResultSets<indexterm>behavior of with auto-commit</indexterm></indexterm>
+</keywords>
+</metadata></prolog>
+<conbody>
+<p>Except for the result sets associated with holdable cursors (see <xref
+href="rdevconceptsholdablecursors.dita#rdevconceptsholdablecursors"></xref> for
+more information), issuing a commit will cause all result sets on your connection
+to be closed.</p>
+<p>The JDBC program is not required to have auto-commit off when using updatable
+ResultSets.<?Pub Caret?></p>
+</conbody>
+</concept>
+<?Pub *0000001456?>

Propchange: incubator/derby/docs/trunk/src/devguide/cdevconcepts23987.dita
------------------------------------------------------------------------------
    svn:eol-style = native

Modified: incubator/derby/docs/trunk/src/devguide/cdevconcepts24019.dita
URL: http://svn.apache.org/viewcvs/incubator/derby/docs/trunk/src/devguide/cdevconcepts24019.dita?view=diff&r1=159547&r2=159548
==============================================================================
--- incubator/derby/docs/trunk/src/devguide/cdevconcepts24019.dita (original)
+++ incubator/derby/docs/trunk/src/devguide/cdevconcepts24019.dita Wed Mar 30 16:26:36 2005
@@ -1,38 +1,38 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!-- 
-Copyright 1997, 2004 The Apache Software Foundation or its licensors, as applicable.  
-
-Licensed under the Apache License, Version 2.0 (the "License");  
-you may not use this file except in compliance with the License.  
-You may obtain a copy of the License at      
-
-   http://www.apache.org/licenses/LICENSE-2.0  
-
-Unless required by applicable law or agreed to in writing, software  
-distributed under the License is distributed on an "AS IS" BASIS,  
-WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.  
-See the License for the specific language governing permissions and  
-limitations under the License.
--->
-<!DOCTYPE concept PUBLIC "-//IBM//DTD DITA Concept//EN" "../dtd/concept.dtd">
-<concept xml:lang="en-us" id="cdevconcepts24019">
-<title>Multiple connections from a single application</title>
-<prolog>
-</prolog>
-<conbody>
-<p>A single application can work with multiple <i>Connections</i> to the same database and assign them to different threads. The application
-programmer can avoid concurrency and deadlock problems in several ways:</p>
-<ul>
-<li>Use the <i>TRANSACTION_READ_COMMITTED</i> isolation level
-and turn on row-level locking (the defaults).</li>
-<li>Beware of deadlocks caused by using more than one <i>Connection</i> in a single thread (the most obvious case). For example, if
-the thread tries to update the same table from two different <codeph><i>Connections</i></codeph>, a deadlock can occur.</li>
-<li>Assign <i>Connections</i> to threads that handle discrete
-tasks. For example, do not have two threads update the <i>Hotels</i> table. Have one thread update the <i>Hotels</i> table
-and a different one update the <i>Groups</i> table.</li>
-<li>If threads access the same tables, commit transactions often.</li>
-<li>Multi-threaded Java applications have the ability to self-deadlock without
-even accessing a database, so beware of that too.</li>
-<li>Use nested connections to share the same lock space.</li>
-</ul>
-</conbody></concept>
+<?xml version="1.0" encoding="utf-8"?>
+<!-- 
+Copyright 1997, 2004 The Apache Software Foundation or its licensors, as applicable.  
+
+Licensed under the Apache License, Version 2.0 (the "License");  
+you may not use this file except in compliance with the License.  
+You may obtain a copy of the License at      
+
+   http://www.apache.org/licenses/LICENSE-2.0  
+
+Unless required by applicable law or agreed to in writing, software  
+distributed under the License is distributed on an "AS IS" BASIS,  
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.  
+See the License for the specific language governing permissions and  
+limitations under the License.
+-->
+<!DOCTYPE concept PUBLIC "-//IBM//DTD DITA Concept//EN" "../dtd/concept.dtd">
+<concept xml:lang="en-us" id="cdevconcepts24019">
+<title>Multiple connections from a single application</title>
+<prolog>
+</prolog>
+<conbody>
+<p>A single application can work with multiple <i>Connections</i> to the same database and assign them to different threads. The application
+programmer can avoid concurrency and deadlock problems in several ways:</p>
+<ul>
+<li>Use the <i>TRANSACTION_READ_COMMITTED</i> isolation level
+and turn on row-level locking (the defaults).</li>
+<li>Beware of deadlocks caused by using more than one <i>Connection</i> in a single thread (the most obvious case). For example, if
+the thread tries to update the same table from two different <codeph><i>Connections</i></codeph>, a deadlock can occur.</li>
+<li>Assign <i>Connections</i> to threads that handle discrete
+tasks. For example, do not have two threads update the <i>Hotels</i> table. Have one thread update the <i>Hotels</i> table
+and a different one update the <i>Groups</i> table.</li>
+<li>If threads access the same tables, commit transactions often.</li>
+<li>Multi-threaded Java applications have the ability to self-deadlock without
+even accessing a database, so beware of that too.</li>
+<li>Use nested connections to share the same lock space.</li>
+</ul>
+</conbody></concept>

Propchange: incubator/derby/docs/trunk/src/devguide/cdevconcepts24019.dita
------------------------------------------------------------------------------
    svn:eol-style = native

Modified: incubator/derby/docs/trunk/src/devguide/cdevconcepts24927.dita
URL: http://svn.apache.org/viewcvs/incubator/derby/docs/trunk/src/devguide/cdevconcepts24927.dita?view=diff&r1=159547&r2=159548
==============================================================================
--- incubator/derby/docs/trunk/src/devguide/cdevconcepts24927.dita (original)
+++ incubator/derby/docs/trunk/src/devguide/cdevconcepts24927.dita Wed Mar 30 16:26:36 2005
@@ -1,29 +1,29 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!-- 
-Copyright 1997, 2004 The Apache Software Foundation or its licensors, as applicable.  
-
-Licensed under the Apache License, Version 2.0 (the "License");  
-you may not use this file except in compliance with the License.  
-You may obtain a copy of the License at      
-
-   http://www.apache.org/licenses/LICENSE-2.0  
-
-Unless required by applicable law or agreed to in writing, software  
-distributed under the License is distributed on an "AS IS" BASIS,  
-WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.  
-See the License for the specific language governing permissions and  
-limitations under the License.
--->
-<!DOCTYPE concept PUBLIC "-//IBM//DTD DITA Concept//EN" "../dtd/concept.dtd">
-<concept xml:lang="en-us" id="cdevconcepts24927">
-<title>Working with Derby SQLExceptions in an Application</title>
-<prolog><metadata>
-<keywords>
-<indexterm>SQLExceptions<indexterm>working with</indexterm></indexterm>
-</keywords>
-</metadata>
-</prolog>
-<conbody>
-<p>JDBC generates exceptions of the type <i>java.sql.SQLException</i>. To see the exceptions generated by <ph conref="devconrefs.dita#prod/productshortname"></ph>, retrieve and process
-the <codeph><i>SQLExceptions</i></codeph> in a catch block.</p>
-</conbody></concept>
+<?xml version="1.0" encoding="utf-8"?>
+<!-- 
+Copyright 1997, 2004 The Apache Software Foundation or its licensors, as applicable.  
+
+Licensed under the Apache License, Version 2.0 (the "License");  
+you may not use this file except in compliance with the License.  
+You may obtain a copy of the License at      
+
+   http://www.apache.org/licenses/LICENSE-2.0  
+
+Unless required by applicable law or agreed to in writing, software  
+distributed under the License is distributed on an "AS IS" BASIS,  
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.  
+See the License for the specific language governing permissions and  
+limitations under the License.
+-->
+<!DOCTYPE concept PUBLIC "-//IBM//DTD DITA Concept//EN" "../dtd/concept.dtd">
+<concept xml:lang="en-us" id="cdevconcepts24927">
+<title>Working with Derby SQLExceptions in an Application</title>
+<prolog><metadata>
+<keywords>
+<indexterm>SQLExceptions<indexterm>working with</indexterm></indexterm>
+</keywords>
+</metadata>
+</prolog>
+<conbody>
+<p>JDBC generates exceptions of the type <i>java.sql.SQLException</i>. To see the exceptions generated by <ph conref="devconrefs.dita#prod/productshortname"></ph>, retrieve and process
+the <codeph><i>SQLExceptions</i></codeph> in a catch block.</p>
+</conbody></concept>

Propchange: incubator/derby/docs/trunk/src/devguide/cdevconcepts24927.dita
------------------------------------------------------------------------------
    svn:eol-style = native

Modified: incubator/derby/docs/trunk/src/devguide/cdevconcepts26633.dita
URL: http://svn.apache.org/viewcvs/incubator/derby/docs/trunk/src/devguide/cdevconcepts26633.dita?view=diff&r1=159547&r2=159548
==============================================================================
--- incubator/derby/docs/trunk/src/devguide/cdevconcepts26633.dita (original)
+++ incubator/derby/docs/trunk/src/devguide/cdevconcepts26633.dita Wed Mar 30 16:26:36 2005
@@ -1,30 +1,30 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!-- 
-Copyright 1997, 2004 The Apache Software Foundation or its licensors, as applicable.  
-
-Licensed under the Apache License, Version 2.0 (the "License");  
-you may not use this file except in compliance with the License.  
-You may obtain a copy of the License at      
-
-   http://www.apache.org/licenses/LICENSE-2.0  
-
-Unless required by applicable law or agreed to in writing, software  
-distributed under the License is distributed on an "AS IS" BASIS,  
-WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.  
-See the License for the specific language governing permissions and  
-limitations under the License.
--->
-<!DOCTYPE concept PUBLIC "-//IBM//DTD DITA Concept//EN" "../dtd/concept.dtd">
-<concept xml:lang="en-us" id="cdevconcepts26633">
-<title>Nested connections</title>
-<prolog><metadata>
-<keywords>
-<indexterm>Nested connections<indexterm>definition</indexterm></indexterm>
-</keywords>
-</metadata>
-</prolog>
-<conbody>
-<p>SQL statements can include routine invocations. If these routines
-interact with the database, they must use a <i>Connection</i>.</p>
-<p>For more information, see <xref href="cdevspecial42117.dita#cdevspecial42117"/>.</p>
-</conbody></concept>
+<?xml version="1.0" encoding="utf-8"?>
+<!-- 
+Copyright 1997, 2004 The Apache Software Foundation or its licensors, as applicable.  
+
+Licensed under the Apache License, Version 2.0 (the "License");  
+you may not use this file except in compliance with the License.  
+You may obtain a copy of the License at      
+
+   http://www.apache.org/licenses/LICENSE-2.0  
+
+Unless required by applicable law or agreed to in writing, software  
+distributed under the License is distributed on an "AS IS" BASIS,  
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.  
+See the License for the specific language governing permissions and  
+limitations under the License.
+-->
+<!DOCTYPE concept PUBLIC "-//IBM//DTD DITA Concept//EN" "../dtd/concept.dtd">
+<concept xml:lang="en-us" id="cdevconcepts26633">
+<title>Nested connections</title>
+<prolog><metadata>
+<keywords>
+<indexterm>Nested connections<indexterm>definition</indexterm></indexterm>
+</keywords>
+</metadata>
+</prolog>
+<conbody>
+<p>SQL statements can include routine invocations. If these routines
+interact with the database, they must use a <i>Connection</i>.</p>
+<p>For more information, see <xref href="cdevspecial42117.dita#cdevspecial42117"/>.</p>
+</conbody></concept>

Propchange: incubator/derby/docs/trunk/src/devguide/cdevconcepts26633.dita
------------------------------------------------------------------------------
    svn:eol-style = native

Modified: incubator/derby/docs/trunk/src/devguide/cdevconcepts28351.dita
URL: http://svn.apache.org/viewcvs/incubator/derby/docs/trunk/src/devguide/cdevconcepts28351.dita?view=diff&r1=159547&r2=159548
==============================================================================
--- incubator/derby/docs/trunk/src/devguide/cdevconcepts28351.dita (original)
+++ incubator/derby/docs/trunk/src/devguide/cdevconcepts28351.dita Wed Mar 30 16:26:36 2005
@@ -1,31 +1,31 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!-- 
-Copyright 1997, 2004 The Apache Software Foundation or its licensors, as applicable.  
-
-Licensed under the Apache License, Version 2.0 (the "License");  
-you may not use this file except in compliance with the License.  
-You may obtain a copy of the License at      
-
-   http://www.apache.org/licenses/LICENSE-2.0  
-
-Unless required by applicable law or agreed to in writing, software  
-distributed under the License is distributed on an "AS IS" BASIS,  
-WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.  
-See the License for the specific language governing permissions and  
-limitations under the License.
--->
-<!DOCTYPE concept PUBLIC "-//IBM//DTD DITA Concept//EN" "../dtd/concept.dtd">
-<concept xml:lang="en-us" id="cdevconcepts28351">
-<title>Updatable cursors</title>
-<prolog>
-</prolog>
-<conbody>
-<p>Cursors are read-only by default. For a cursor to be updatable, you must
-specify SELECT . . . FOR UPDATE. Use FOR UPDATE only when you will be modifying
-rows to avoid excessive locking of tables.</p>
-<ul>
-<li><xref href="cdevconcepts30811.dita#cdevconcepts30811"/></li>
-<li><xref href="tdevconcepts41704.dita#tdevconcepts41704"/></li>
-<li><xref href="rdevconcepts38274.dita#rdevconcepts38274"/></li>
-</ul>
-</conbody></concept>
+<?xml version="1.0" encoding="utf-8"?>
+<!-- 
+Copyright 1997, 2004 The Apache Software Foundation or its licensors, as applicable.  
+
+Licensed under the Apache License, Version 2.0 (the "License");  
+you may not use this file except in compliance with the License.  
+You may obtain a copy of the License at      
+
+   http://www.apache.org/licenses/LICENSE-2.0  
+
+Unless required by applicable law or agreed to in writing, software  
+distributed under the License is distributed on an "AS IS" BASIS,  
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.  
+See the License for the specific language governing permissions and  
+limitations under the License.
+-->
+<!DOCTYPE concept PUBLIC "-//IBM//DTD DITA Concept//EN" "../dtd/concept.dtd">
+<concept xml:lang="en-us" id="cdevconcepts28351">
+<title>Updatable cursors</title>
+<prolog>
+</prolog>
+<conbody>
+<p>Cursors are read-only by default. For a cursor to be updatable, you must
+specify SELECT . . . FOR UPDATE. Use FOR UPDATE only when you will be modifying
+rows to avoid excessive locking of tables.</p>
+<ul>
+<li><xref href="cdevconcepts30811.dita#cdevconcepts30811"/></li>
+<li><xref href="tdevconcepts41704.dita#tdevconcepts41704"/></li>
+<li><xref href="rdevconcepts38274.dita#rdevconcepts38274"/></li>
+</ul>
+</conbody></concept>

Propchange: incubator/derby/docs/trunk/src/devguide/cdevconcepts28351.dita
------------------------------------------------------------------------------
    svn:eol-style = native

Modified: incubator/derby/docs/trunk/src/devguide/cdevconcepts28436.dita
URL: http://svn.apache.org/viewcvs/incubator/derby/docs/trunk/src/devguide/cdevconcepts28436.dita?view=diff&r1=159547&r2=159548
==============================================================================
--- incubator/derby/docs/trunk/src/devguide/cdevconcepts28436.dita (original)
+++ incubator/derby/docs/trunk/src/devguide/cdevconcepts28436.dita Wed Mar 30 16:26:36 2005
@@ -1,46 +1,46 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!-- 
-Copyright 1997, 2004 The Apache Software Foundation or its licensors, as applicable.  
-
-Licensed under the Apache License, Version 2.0 (the "License");  
-you may not use this file except in compliance with the License.  
-You may obtain a copy of the License at      
-
-   http://www.apache.org/licenses/LICENSE-2.0  
-
-Unless required by applicable law or agreed to in writing, software  
-distributed under the License is distributed on an "AS IS" BASIS,  
-WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.  
-See the License for the specific language governing permissions and  
-limitations under the License.
--->
-<!DOCTYPE concept PUBLIC "-//IBM//DTD DITA Concept//EN" "../dtd/concept.dtd">
-<concept xml:lang="en-us" id="cdevconcepts28436">
-<title>Deadlocks</title>
-<prolog><metadata>
-<keywords>
-<indexterm>Deadlocks<indexterm>description</indexterm></indexterm>
-</keywords>
-</metadata>
-</prolog>
-<conbody>
-<p>In a database, a deadlock is a situation in which two or more transactions
-are waiting for one another to give up locks.</p>
-<p>For example, Transaction A might hold a lock on some rows in the <i>Accounts</i> table and needs to update some rows in the <i>Orders</i> table to finish. Transaction B holds locks on those very rows
-in the <i>Orders</i> table but needs to update the rows in
-the <i>Accounts</i> table held by Transaction A. Transaction
-A cannot complete its transaction because of the lock on <i>Orders</i>. Transaction B cannot complete its transaction because of the
-lock on <i>Accounts</i>. All activity comes to a halt and
-remains at a standstill forever unless the DBMS detects the deadlock and aborts
-one of the transactions.</p>
-<fig expanse="column">
-<title>A deadlock.</title><image placement="break" href="dead.gif"><alt>This figure depicts a deadlock, where two transactions are waiting for one another to give up locks.</alt></image></fig>
-<ul>
-<li><xref href="cdevconcepts53677.dita#cdevconcepts53677"/></li>
-<li><xref href="cdevconcepts95005.dita#cdevconcepts95005"/></li>
-<li><xref href="cdevconcepts89097.dita#cdevconcepts89097"/></li>
-<li><xref href="cdevconcepts16400.dita#cdevconcepts16400"/></li>
-<li><xref href="cdevconcepts50894.dita#cdevconcepts50894"/></li>
-<li><xref href="cdevconcepts32861.dita#cdevconcepts32861"/></li>
-</ul>
-</conbody></concept>
+<?xml version="1.0" encoding="utf-8"?>
+<!-- 
+Copyright 1997, 2004 The Apache Software Foundation or its licensors, as applicable.  
+
+Licensed under the Apache License, Version 2.0 (the "License");  
+you may not use this file except in compliance with the License.  
+You may obtain a copy of the License at      
+
+   http://www.apache.org/licenses/LICENSE-2.0  
+
+Unless required by applicable law or agreed to in writing, software  
+distributed under the License is distributed on an "AS IS" BASIS,  
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.  
+See the License for the specific language governing permissions and  
+limitations under the License.
+-->
+<!DOCTYPE concept PUBLIC "-//IBM//DTD DITA Concept//EN" "../dtd/concept.dtd">
+<concept xml:lang="en-us" id="cdevconcepts28436">
+<title>Deadlocks</title>
+<prolog><metadata>
+<keywords>
+<indexterm>Deadlocks<indexterm>description</indexterm></indexterm>
+</keywords>
+</metadata>
+</prolog>
+<conbody>
+<p>In a database, a deadlock is a situation in which two or more transactions
+are waiting for one another to give up locks.</p>
+<p>For example, Transaction A might hold a lock on some rows in the <i>Accounts</i> table and needs to update some rows in the <i>Orders</i> table to finish. Transaction B holds locks on those very rows
+in the <i>Orders</i> table but needs to update the rows in
+the <i>Accounts</i> table held by Transaction A. Transaction
+A cannot complete its transaction because of the lock on <i>Orders</i>. Transaction B cannot complete its transaction because of the
+lock on <i>Accounts</i>. All activity comes to a halt and
+remains at a standstill forever unless the DBMS detects the deadlock and aborts
+one of the transactions.</p>
+<fig expanse="column">
+<title>A deadlock.</title><image placement="break" href="dead.gif"><alt>This figure depicts a deadlock, where two transactions are waiting for one another to give up locks.</alt></image></fig>
+<ul>
+<li><xref href="cdevconcepts53677.dita#cdevconcepts53677"/></li>
+<li><xref href="cdevconcepts95005.dita#cdevconcepts95005"/></li>
+<li><xref href="cdevconcepts89097.dita#cdevconcepts89097"/></li>
+<li><xref href="cdevconcepts16400.dita#cdevconcepts16400"/></li>
+<li><xref href="cdevconcepts50894.dita#cdevconcepts50894"/></li>
+<li><xref href="cdevconcepts32861.dita#cdevconcepts32861"/></li>
+</ul>
+</conbody></concept>

Propchange: incubator/derby/docs/trunk/src/devguide/cdevconcepts28436.dita
------------------------------------------------------------------------------
    svn:eol-style = native



Mime
View raw message