List:Commits« Previous MessageNext Message »
From:paul Date:June 9 2008 8:05pm
Subject:svn commit - mysqldoc@docsrva: r10921 - in trunk: . it/refman-5.1 pt/refman-5.1 refman-4.1 refman-5.0 refman-5.1 refman-6.0
View as plain text  
Author: paul
Date: 2008-06-09 22:05:03 +0200 (Mon, 09 Jun 2008)
New Revision: 10921

Log:
 r31916@frost:  paul | 2008-06-09 14:13:00 -0500
 WRITE lock also allows reading by lock holder


Modified:
   trunk/it/refman-5.1/sql-syntax.xml
   trunk/pt/refman-5.1/sql-syntax.xml
   trunk/refman-4.1/sql-syntax.xml
   trunk/refman-5.0/sql-syntax.xml
   trunk/refman-5.1/sql-syntax.xml
   trunk/refman-6.0/lock-tables-tmp.xml
   trunk/refman-6.0/sql-syntax.xml

Property changes on: trunk
___________________________________________________________________
Name: svk:merge
   - 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:35828
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:31902
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:31613
   + 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:35828
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:31916
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:31613


Modified: trunk/it/refman-5.1/sql-syntax.xml
===================================================================
--- trunk/it/refman-5.1/sql-syntax.xml	2008-06-09 16:50:28 UTC (rev 10920)
+++ trunk/it/refman-5.1/sql-syntax.xml	2008-06-09 20:05:03 UTC (rev 10921)
Changed blocks: 1, Lines Added: 4, Lines Deleted: 3; 936 bytes

@@ -15100,9 +15100,10 @@
         If a thread obtains a <literal>READ</literal> lock on a table,
         that thread (and all other threads) can only read from the
         table. If a thread obtains a <literal>WRITE</literal> lock on a
-        table, only the thread holding the lock can write to the table.
-        Other threads are blocked from reading or writing the table
-        until the lock has been released.
+        table, only the thread holding the lock can write to the table
+        (that thread can also read from the table). Other threads are
+        blocked from reading or writing the table until the lock has
+        been released.
       </para>
 
       <para>


Modified: trunk/pt/refman-5.1/sql-syntax.xml
===================================================================
--- trunk/pt/refman-5.1/sql-syntax.xml	2008-06-09 16:50:28 UTC (rev 10920)
+++ trunk/pt/refman-5.1/sql-syntax.xml	2008-06-09 20:05:03 UTC (rev 10921)
Changed blocks: 1, Lines Added: 4, Lines Deleted: 3; 936 bytes

@@ -15100,9 +15100,10 @@
         If a thread obtains a <literal>READ</literal> lock on a table,
         that thread (and all other threads) can only read from the
         table. If a thread obtains a <literal>WRITE</literal> lock on a
-        table, only the thread holding the lock can write to the table.
-        Other threads are blocked from reading or writing the table
-        until the lock has been released.
+        table, only the thread holding the lock can write to the table
+        (that thread can also read from the table). Other threads are
+        blocked from reading or writing the table until the lock has
+        been released.
       </para>
 
       <para>


Modified: trunk/refman-4.1/sql-syntax.xml
===================================================================
--- trunk/refman-4.1/sql-syntax.xml	2008-06-09 16:50:28 UTC (rev 10920)
+++ trunk/refman-4.1/sql-syntax.xml	2008-06-09 20:05:03 UTC (rev 10921)
Changed blocks: 1, Lines Added: 4, Lines Deleted: 3; 927 bytes

@@ -11620,9 +11620,10 @@
         If a thread obtains a <literal>READ</literal> lock on a table,
         that thread (and all other threads) can only read from the
         table. If a thread obtains a <literal>WRITE</literal> lock on a
-        table, only the thread holding the lock can write to the table.
-        Other threads are blocked from reading or writing the table
-        until the lock has been released.
+        table, only the thread holding the lock can write to the table
+        (that thread can also read from the table). Other threads are
+        blocked from reading or writing the table until the lock has
+        been released.
       </para>
 
       <para>


Modified: trunk/refman-5.0/sql-syntax.xml
===================================================================
--- trunk/refman-5.0/sql-syntax.xml	2008-06-09 16:50:28 UTC (rev 10920)
+++ trunk/refman-5.0/sql-syntax.xml	2008-06-09 20:05:03 UTC (rev 10921)
Changed blocks: 1, Lines Added: 4, Lines Deleted: 3; 927 bytes

@@ -12523,9 +12523,10 @@
         If a thread obtains a <literal>READ</literal> lock on a table,
         that thread (and all other threads) can only read from the
         table. If a thread obtains a <literal>WRITE</literal> lock on a
-        table, only the thread holding the lock can write to the table.
-        Other threads are blocked from reading or writing the table
-        until the lock has been released.
+        table, only the thread holding the lock can write to the table
+        (that thread can also read from the table). Other threads are
+        blocked from reading or writing the table until the lock has
+        been released.
       </para>
 
       <para>


Modified: trunk/refman-5.1/sql-syntax.xml
===================================================================
--- trunk/refman-5.1/sql-syntax.xml	2008-06-09 16:50:28 UTC (rev 10920)
+++ trunk/refman-5.1/sql-syntax.xml	2008-06-09 20:05:03 UTC (rev 10921)
Changed blocks: 1, Lines Added: 4, Lines Deleted: 3; 927 bytes

@@ -15100,9 +15100,10 @@
         If a thread obtains a <literal>READ</literal> lock on a table,
         that thread (and all other threads) can only read from the
         table. If a thread obtains a <literal>WRITE</literal> lock on a
-        table, only the thread holding the lock can write to the table.
-        Other threads are blocked from reading or writing the table
-        until the lock has been released.
+        table, only the thread holding the lock can write to the table
+        (that thread can also read from the table). Other threads are
+        blocked from reading or writing the table until the lock has
+        been released.
       </para>
 
       <para>


Modified: trunk/refman-6.0/lock-tables-tmp.xml
===================================================================
--- trunk/refman-6.0/lock-tables-tmp.xml	2008-06-09 16:50:28 UTC (rev 10920)
+++ trunk/refman-6.0/lock-tables-tmp.xml	2008-06-09 20:05:03 UTC (rev 10921)
Changed blocks: 2, Lines Added: 11, Lines Deleted: 11; 1885 bytes

@@ -40,13 +40,12 @@
 </programlisting>
 
   <para>
-    [ TODO: Discuss name locks in optimizer chapter? We don't say
-    whether the holder of a WRITE lock also can read the locked table.
-    It's not true that you cannot access any non-locked table while you
-    hold locks: You can access TEMPORARY tables. LOCK TABLES appears to
-    lock TEMPORARY tables, but should you even bother, given the
-    preceding sentence? How do transactional lock requests and requests
-    to enable read_only interact? ]
+    [ TODO: Discuss name locks in optimizer chapter? It's not true that
+    you cannot access any non-locked table while you hold locks: You can
+    access TEMPORARY tables. LOCK TABLES appears to lock TEMPORARY
+    tables, but should you even bother, given the preceding sentence?
+    How do transactional lock requests and requests to enable read_only
+    interact? ]
   </para>
 
   <remark role="help-description-begin"/>

@@ -90,10 +89,11 @@
     <listitem>
       <para>
         <literal>[LOW_PRIORITY] WRITE</literal>: Locks a table for
-        writing. Only one client at a time can acquire a
-        <literal>WRITE</literal> lock for a table. The
-        <literal>LOW_PRIORITY</literal> modifier affects lock scheduling
-        if the <literal>WRITE</literal> lock request must wait.
+        writing. The holder of the lock can also read the table. Only
+        one client at a time can acquire a <literal>WRITE</literal> lock
+        for a table. The <literal>LOW_PRIORITY</literal> modifier
+        affects lock scheduling if the <literal>WRITE</literal> lock
+        request must wait.
       </para>
 
       <para>


Modified: trunk/refman-6.0/sql-syntax.xml
===================================================================
--- trunk/refman-6.0/sql-syntax.xml	2008-06-09 16:50:28 UTC (rev 10920)
+++ trunk/refman-6.0/sql-syntax.xml	2008-06-09 20:05:03 UTC (rev 10921)
Changed blocks: 1, Lines Added: 4, Lines Deleted: 3; 927 bytes

@@ -15586,9 +15586,10 @@
         If a thread obtains a <literal>READ</literal> lock on a table,
         that thread (and all other threads) can only read from the
         table. If a thread obtains a <literal>WRITE</literal> lock on a
-        table, only the thread holding the lock can write to the table.
-        Other threads are blocked from reading or writing the table
-        until the lock has been released.
+        table, only the thread holding the lock can write to the table
+        (that thread can also read from the table). Other threads are
+        blocked from reading or writing the table until the lock has
+        been released.
       </para>
 
       <para>


Thread
svn commit - mysqldoc@docsrva: r10921 - in trunk: . it/refman-5.1 pt/refman-5.1 refman-4.1 refman-5.0 refman-5.1 refman-6.0paul9 Jun