bk commit - mysqldoc@docsrva tree (paul:1.3250)

[paul]

Below is the list of changes that have just been committed into a local
mysqldoc repository of paul. When paul does a push these changes will
be propagated to the main repository and, within 24 hours after the
push, to the public repository.
For information on how to access the public repository
see http://www.mysql.com/doc/I/n/Installing_source_tree.html

ChangeSet
  1.3250 05/08/12 15:35:13 paul@stripped +3 -0
  Statements use a snapshot of available routines and
  triggers during execution.

  refman/restrictions.xml
    1.8 05/08/12 15:35:12 paul@stripped +11 -0
    Statements use a snapshot of available routines and
    triggers during execution.

  refman-5.1/restrictions.xml
    1.3 05/08/12 15:35:12 paul@stripped +11 -0
    Sync.

  refman-5.0/restrictions.xml
    1.3 05/08/12 15:35:12 paul@stripped +11 -0
    Sync.

# This is a BitKeeper patch.  What follows are the unified diffs for the
# set of deltas contained in the patch.  The rest of the patch, the part
# that BitKeeper cares about, is below these diffs.
# User:	paul
# Host:	kite-hub.kitebird.com
# Root:	/src/extern/MySQL/bk/mysqldoc

--- 1.2/refman-5.1/restrictions.xml	2005-08-08 21:53:07 -05:00
+++ 1.3/refman-5.1/restrictions.xml	2005-08-12 15:35:12 -05:00
@@ -152,6 +152,17 @@
       statements.
     </para>
 
+    <para>
+      To prevent problems of interaction between server threads, when a
+      client issues a statement, the server uses a snapshot of routines
+      and triggers available for execution of the statement. That is,
+      the server calculates a list of procedures, functions, and
+      triggers that may be used during execution of the statement, loads
+      them, and then proceeds to execute the statement. This means that
+      while the statement executes, it will not see changes to routines
+      performed by other threads.
+    </para>
+
   </section>
 
   <section id="cursor-restrictions">

--- 1.7/refman/restrictions.xml	2005-08-08 21:53:16 -05:00
+++ 1.8/refman/restrictions.xml	2005-08-12 15:35:12 -05:00
@@ -152,6 +152,17 @@
       statements.
     </para>
 
+    <para>
+      To prevent problems of interaction between server threads, when a
+      client issues a statement, the server uses a snapshot of routines
+      and triggers available for execution of the statement. That is,
+      the server calculates a list of procedures, functions, and
+      triggers that may be used during execution of the statement, loads
+      them, and then proceeds to execute the statement. This means that
+      while the statement executes, it will not see changes to routines
+      performed by other threads.
+    </para>
+
   </section>
 
   <section id="cursor-restrictions">

--- 1.2/refman-5.0/restrictions.xml	2005-08-08 21:53:02 -05:00
+++ 1.3/refman-5.0/restrictions.xml	2005-08-12 15:35:12 -05:00
@@ -152,6 +152,17 @@
       statements.
     </para>
 
+    <para>
+      To prevent problems of interaction between server threads, when a
+      client issues a statement, the server uses a snapshot of routines
+      and triggers available for execution of the statement. That is,
+      the server calculates a list of procedures, functions, and
+      triggers that may be used during execution of the statement, loads
+      them, and then proceeds to execute the statement. This means that
+      while the statement executes, it will not see changes to routines
+      performed by other threads.
+    </para>
+
   </section>
 
   <section id="cursor-restrictions">