db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From chaa...@apache.org
Subject svn commit: r1531012 - /db/derby/docs/branches/10.10/src/devguide/cdevconcepts53677.dita
Date Thu, 10 Oct 2013 15:05:46 GMT
Author: chaase3
Date: Thu Oct 10 15:05:46 2013
New Revision: 1531012

URL: http://svn.apache.org/r1531012
DERBY-6375  Suggest use of indexes in devguide's deadlock avoidance topic

Merged patch DERBY-6375-2.diff to 10.10 doc branch from trunk revision 1531008.


Modified: db/derby/docs/branches/10.10/src/devguide/cdevconcepts53677.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/branches/10.10/src/devguide/cdevconcepts53677.dita?rev=1531012&r1=1531011&r2=1531012&view=diff
--- db/derby/docs/branches/10.10/src/devguide/cdevconcepts53677.dita (original)
+++ db/derby/docs/branches/10.10/src/devguide/cdevconcepts53677.dita Thu Oct 10 15:05:46 2013
@@ -33,9 +33,16 @@ in the same order. That way, in the scen
 B simply waits for transaction A to release the lock on <i>Orders</i> before
 it begins. When transaction A releases the lock on <i>Orders</i>, Transaction
 B can proceed freely.</p>
+<p>The appropriate use of indexes can also help you to avoid deadlocks, since
+indexes make table scans less likely and reduce the number of locks obtained.
+For more information, see "CREATE INDEX statement" in the
+<ph conref="../conrefs.dita#pub/citref"></ph> and the topics under "Avoiding
+table scans of large tables" in
+<ph conref="../conrefs.dita#pub/cittuning"></ph>.</p>
 <p>Another tool available to you is the LOCK TABLE statement. A transaction
 can attempt to lock a table in exclusive mode when it starts to prevent other
 transactions from getting shared locks on a table. For more information, see
-"LOCK TABLE statement" in the <cite><ph conref="../conrefs.dita#pub/citref"></ph></cite>.</p>
+"LOCK TABLE statement" in the
+<ph conref="../conrefs.dita#pub/citref"></ph>.</p>

View raw message