From: john.russell
Date: June 15 2010 8:10pm
Subject: svn commit - mysqldoc@docsrva: r21254 - trunk/refman-5.1
List-Archive: http://lists.mysql.com/commits/111194
Message-Id: <201006152010.o5FKAqER015673@docsrva.mysql.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Author: jrussell
Date: 2010-06-15 22:10:52 +0200 (Tue, 15 Jun 2010)
New Revision: 21254

Log:
Clarified relationship between prepared statements and dynamic SQL.


Modified:
   trunk/refman-5.1/restrictions.xml


Modified: trunk/refman-5.1/restrictions.xml
===================================================================
--- trunk/refman-5.1/restrictions.xml	2010-06-15 16:46:38 UTC (rev 21253)
+++ trunk/refman-5.1/restrictions.xml	2010-06-15 20:10:52 UTC (rev 21254)
Changed blocks: 2, Lines Added: 9, Lines Deleted: 9; 1309 bytes

@@ -133,15 +133,6 @@
 
       <listitem>
         <para>
-          Before MySQL 5.1.4, <literal role="stmt">CALL</literal>
-          statements cannot be prepared. This is true both for
-          server-side prepared statements and for SQL prepared
-          statements.
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
           Inserts cannot be delayed. <literal role="stmt">INSERT
           DELAYED</literal> syntax is accepted, but the statement is
           handled as a normal <literal role="stmt">INSERT</literal>.

@@ -287,6 +278,15 @@
 
     </itemizedlist>
 
+    <bridgehead>Restrictions on Calling Stored Procedures</bridgehead>
+
+    <para>
+      Before MySQL 5.1.4, <literal role="stmt">CALL</literal> statements
+      cannot be prepared, meaning that stored procedures cannot be
+      called from dynamic SQL. This is true both for server-side
+      prepared statements and for SQL prepared statements.
+    </para>
+
     <bridgehead id="stored-routine-name-conflicts">Name Conflicts within Stored Routines</bridgehead>
 
     <para>