MySQL Lists are EOL. Please join:

List:Commits« Previous MessageNext Message »
From:jon Date:December 4 2007 8:13pm
Subject:svn commit - mysqldoc@docsrva: r9102 - trunk/refman-6.0
View as plain text  
Author: jstephens
Date: 2007-12-04 21:13:31 +0100 (Tue, 04 Dec 2007)
New Revision: 9102

Log:

LOCK TABLE syntax has been extended in 6.0; the traditional syntax 
retains the old behaviour

Fixes Docs Bug #32947



Modified:
   trunk/refman-6.0/introduction.xml


Modified: trunk/refman-6.0/introduction.xml
===================================================================
--- trunk/refman-6.0/introduction.xml	2007-12-04 19:47:19 UTC (rev 9101)
+++ trunk/refman-6.0/introduction.xml	2007-12-04 20:13:31 UTC (rev 9102)
Changed blocks: 1, Lines Added: 19, Lines Deleted: 8; 2099 bytes

@@ -425,16 +425,27 @@
 
           <listitem>
             <para>
-              The <literal>LOCK TABLE</literal> statement no longer
-              commits transactions automatically. Following
-              <literal>LOCK TABLE</literal>, you can now access tables
-              not mentioned in the <literal>LOCK TABLE</literal>
-              statement. You can now also issue <literal>LOCK
-              TABLE</literal> many times in succession, adding
-              additional tables to the locked set, and without unlocking
-              any tables that were locked previously; tables are not
+              The syntax for the <literal>LOCK TABLE</literal> statement
+              has been extended to support transactional table locks
+              which do not commit transactions automatically. Following
+              <literal>LOCK TABLE ... IN SHARE MODE</literal> or
+              <literal>LOCK TABLE ... IN EXCLUSIVE MODE</literal>, you
+              can access tables not mentioned in the <literal>LOCK
+              TABLE</literal> statement. You can now also issue these
+              extended <literal>LOCK TABLE</literal> statements many
+              times in succession, adding additional tables to the
+              locked set, and without unlocking any tables that were
+              locked previously. When using <literal>LOCK
+              TABLE</literal> with <literal>IN SHARE MODE</literal> or
+              <literal>IN EXCLUSIVE MODE</literal> tables are not
               unlocked until the transaction is committed.
             </para>
+
+            <para>
+              The behavior of <literal>LOCK TABLE</literal> when not
+              using either <literal>IN SHARE MODE</literal> or
+              <literal>IN EXCLUSIVE MODE</literal> remains unchanged.
+            </para>
           </listitem>
 
           <listitem>


Thread
svn commit - mysqldoc@docsrva: r9102 - trunk/refman-6.0jon4 Dec