svn commit - mysqldoc@docsrva: r11286 - in trunk: . refman-5.0 refman-5.1 refman-6.0

[paul]

Author: paul
Date: 2008-07-18 17:41:30 +0200 (Fri, 18 Jul 2008)
New Revision: 11286

Log:
 r32753@frost:  paul | 2008-07-18 10:21:40 -0500
 Fix documentation bug#37541


Modified:
   trunk/refman-5.0/restrictions.xml
   trunk/refman-5.1/restrictions.xml
   trunk/refman-6.0/restrictions.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:32727
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:32322
   + 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:35828
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:32753
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:32322


Modified: trunk/refman-5.0/restrictions.xml
===================================================================
--- trunk/refman-5.0/restrictions.xml	2008-07-18 10:41:06 UTC (rev 11285)
+++ trunk/refman-5.0/restrictions.xml	2008-07-18 15:41:30 UTC (rev 11286)
Changed blocks: 1, Lines Added: 18, Lines Deleted: 0; 1077 bytes

@@ -186,6 +186,24 @@
         </para>
       </listitem>
 
+      <listitem>
+        <para>
+          A stored function acquires table locks before executing, to
+          avoid inconsistency in the binary log due to mismatch of the
+          order in which statements execute and when they appear in the
+          log. Statements that invoke a function are recorded rather
+          than the statements executed within the function.
+          Consequently, stored functions that update the same underlying
+          tables do not execute in parallel.
+        </para>
+
+        <para>
+          In contrast, stored procedures do not acquire table-level
+          locks. All statements executed within stored procedures are
+          written to the binary log.
+        </para>
+      </listitem>
+
     </itemizedlist>
 
     <para>


Modified: trunk/refman-5.1/restrictions.xml
===================================================================
--- trunk/refman-5.1/restrictions.xml	2008-07-18 10:41:06 UTC (rev 11285)
+++ trunk/refman-5.1/restrictions.xml	2008-07-18 15:41:30 UTC (rev 11286)
Changed blocks: 1, Lines Added: 20, Lines Deleted: 0; 1182 bytes

@@ -181,6 +181,26 @@
         </para>
       </listitem>
 
+      <listitem>
+        <para>
+          A stored function acquires table locks before executing, to
+          avoid inconsistency in the binary log due to mismatch of the
+          order in which statements execute and when they appear in the
+          log. When statement-based binary logging is used, statements
+          that invoke a function are recorded rather than the statements
+          executed within the function. Consequently, stored functions
+          that update the same underlying tables do not execute in
+          parallel.
+        </para>
+
+        <para>
+          In contrast, stored procedures do not acquire table-level
+          locks. All statements executed within stored procedures are
+          written to the binary log even for statement-based binary
+          logging.
+        </para>
+      </listitem>
+
     </itemizedlist>
 
     <para>


Modified: trunk/refman-6.0/restrictions.xml
===================================================================
--- trunk/refman-6.0/restrictions.xml	2008-07-18 10:41:06 UTC (rev 11285)
+++ trunk/refman-6.0/restrictions.xml	2008-07-18 15:41:30 UTC (rev 11286)
Changed blocks: 1, Lines Added: 20, Lines Deleted: 0; 1182 bytes

@@ -187,6 +187,26 @@
         </para>
       </listitem>
 
+      <listitem>
+        <para>
+          A stored function acquires table locks before executing, to
+          avoid inconsistency in the binary log due to mismatch of the
+          order in which statements execute and when they appear in the
+          log. When statement-based binary logging is used, statements
+          that invoke a function are recorded rather than the statements
+          executed within the function. Consequently, stored functions
+          that update the same underlying tables do not execute in
+          parallel.
+        </para>
+
+        <para>
+          In contrast, stored procedures do not acquire table-level
+          locks. All statements executed within stored procedures are
+          written to the binary log even for statement-based binary
+          logging.
+        </para>
+      </listitem>
+
     </itemizedlist>
 
     <para>