db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From chaa...@apache.org
Subject svn commit: r1403361 - /db/derby/docs/trunk/src/devguide/cdevconcepts32861.dita
Date Mon, 29 Oct 2012 15:23:41 GMT
Author: chaase3
Date: Mon Oct 29 15:23:40 2012
New Revision: 1403361

URL: http://svn.apache.org/viewvc?rev=1403361&view=rev
DERBY-5961  Developer's guide mentions SQL state 40XL2 which is no longer used

Modified one Developer's Guide file.

Patch: DERBY-5961.diff


Modified: db/derby/docs/trunk/src/devguide/cdevconcepts32861.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevconcepts32861.dita?rev=1403361&r1=1403360&r2=1403361&view=diff
--- db/derby/docs/trunk/src/devguide/cdevconcepts32861.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevconcepts32861.dita Mon Oct 29 15:23:40 2012
@@ -28,8 +28,8 @@ out, you should program your application
-<p>To do this, test for <i>SQLExceptions</i> with <codeph><i>SQLStates</i></codeph>
-40001 (deadlock timeout) or 40XL1 or 40XL2 (lockwait timeout).</p>
+<p>To do this, test for <i>SQLExceptions</i> with <i>SQLStates</i>
of 40001
+(deadlock timeout) or 40XL1 (lockwait timeout).</p>
 <p>In the case of a deadlock you might want to re-try the transaction that
 was chosen as a victim. In the case of a lock wait timeout, you probably do
 not want to do this right away.</p>

View raw message