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

[paul.dubois]

Author: paul
Date: 2008-09-08 21:47:31 +0200 (Mon, 08 Sep 2008)
New Revision: 11736

Log:
 r33057@arctic:  paul | 2008-09-08 14:34:05 -0500
 Revision stored routines intro


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


Modified: trunk/refman-5.0/stored-procedures.xml
===================================================================
--- trunk/refman-5.0/stored-procedures.xml	2008-09-08 19:17:59 UTC (rev 11735)
+++ trunk/refman-5.0/stored-procedures.xml	2008-09-08 19:47:31 UTC (rev 11736)
Changed blocks: 7, Lines Added: 37, Lines Deleted: 21; 4145 bytes

@@ -26,12 +26,6 @@
     the stored procedure instead.
   </para>
 
-  <para>
-    Answers to some questions that are commonly asked regarding stored
-    routines in MySQL can be found in
-    <xref linkend="faqs-stored-procs"/>.
-  </para>
-
   <formalpara role="mnmas">
 
     <title>MySQL Enterprise</title>

@@ -98,22 +92,19 @@
   <para>
     The MySQL implementation of stored routines is still in progress.
     All syntax described in this chapter is supported and any
-    limitations and extensions are documented where appropriate. Further
-    discussion of restrictions on use of stored routines is given in
-    <xref linkend="routine-restrictions"/>.
+    limitations and extensions are documented where appropriate.
   </para>
 
   <para>
-    Binary logging for stored routines takes place as described in
-    <xref linkend="stored-procedure-logging"/>.
+    Stored functions cannot be recursive.
   </para>
 
   <para>
-    Recursive stored procedures are disabled by default, but can be
-    enabled on the server by setting the
+    Recursion in stored procedures is allowed but disabled by default.
+    To enable recursion, set the
     <literal>max_sp_recursion_depth</literal> server system variable to
-    a nonzero value. Stored procedure recursion increases the demand on
-    thread stack space. If you increase the value of
+    a value greater than zero. Stored procedure recursion increases the
+    demand on thread stack space. If you increase the value of
     <literal>max_sp_recursion_depth</literal>, it may be necessary to
     increase thread stack size by increasing the value of
     <literal>thread_stack</literal> at server startup. See

@@ -121,10 +112,35 @@
   </para>
 
   <para>
-    Stored functions cannot be recursive. See
-    <xref linkend="routine-restrictions"/>.
+    <emphasis role="bold">Additional resources</emphasis>
   </para>
 
+  <itemizedlist>
+
+    <listitem>
+      <para>
+        Binary logging for stored routines takes place as described in
+        <xref linkend="stored-procedure-logging"/>.
+      </para>
+    </listitem>
+
+    <listitem>
+      <para>
+        Answers to some questions that are commonly asked regarding
+        stored routines in MySQL can be found in
+        <xref linkend="faqs-stored-procs"/>.
+      </para>
+    </listitem>
+
+    <listitem>
+      <para>
+        Discussion of restrictions on use of stored routines is given in
+        <xref linkend="routine-restrictions"/>.
+      </para>
+    </listitem>
+
+  </itemizedlist>
+
   <section id="stored-procedure-privileges">
 
     <title>Stored Routines and the Grant Tables</title>

@@ -1264,7 +1280,7 @@
       <remark role="help-description-end"/>
 
       <para>
-        The optional <literal>[NOT] ATOMIC</literal> clause is not yet
+        The optional <literal>[NOT] ATOMIC</literal> clause is not
         supported. This means that no transactional savepoint is set at
         the start of the instruction block and the
         <literal>BEGIN</literal> clause used in this context has no

@@ -1617,7 +1633,7 @@
           terminates for the <literal>BEGIN ... END</literal> compound
           statement in which the handler is declared. (This is true even
           if the condition occurs in an inner block.) The
-          <literal>UNDO</literal> handler type statement is not yet
+          <literal>UNDO</literal> handler type statement is not
           supported.
         </para>
 

@@ -1848,7 +1864,7 @@
 
       <para>
         Cursors are supported inside stored procedures and functions and
-        triggers. The syntax is as in embedded SQL. Cursors currently
+        triggers. The syntax is as in embedded SQL. Cursors in MySQL
         have these properties:
       </para>
 

@@ -2074,7 +2090,7 @@
       </para>
 
       <para>
-        <literal>FOR</literal> loops are not currently supported.
+        <literal>FOR</literal> loops are not supported.
       </para>
 
       <section id="if-statement">


Modified: trunk/refman-5.1/stored-procedures.xml
===================================================================
--- trunk/refman-5.1/stored-procedures.xml	2008-09-08 19:17:59 UTC (rev 11735)
+++ trunk/refman-5.1/stored-procedures.xml	2008-09-08 19:47:31 UTC (rev 11736)
Changed blocks: 7, Lines Added: 37, Lines Deleted: 21; 4145 bytes

@@ -26,12 +26,6 @@
     the stored procedure instead.
   </para>
 
-  <para>
-    Answers to some questions that are commonly asked regarding stored
-    routines in MySQL can be found in
-    <xref linkend="faqs-stored-procs"/>.
-  </para>
-
   <formalpara role="mnmas">
 
     <title>MySQL Enterprise</title>

@@ -98,22 +92,19 @@
   <para>
     The MySQL implementation of stored routines is still in progress.
     All syntax described in this chapter is supported and any
-    limitations and extensions are documented where appropriate. Further
-    discussion of restrictions on use of stored routines is given in
-    <xref linkend="routine-restrictions"/>.
+    limitations and extensions are documented where appropriate.
   </para>
 
   <para>
-    Binary logging for stored routines takes place as described in
-    <xref linkend="stored-procedure-logging"/>.
+    Stored functions cannot be recursive.
   </para>
 
   <para>
-    Recursive stored procedures are disabled by default, but can be
-    enabled on the server by setting the
+    Recursion in stored procedures is allowed but disabled by default.
+    To enable recursion, set the
     <literal>max_sp_recursion_depth</literal> server system variable to
-    a nonzero value. Stored procedure recursion increases the demand on
-    thread stack space. If you increase the value of
+    a value greater than zero. Stored procedure recursion increases the
+    demand on thread stack space. If you increase the value of
     <literal>max_sp_recursion_depth</literal>, it may be necessary to
     increase thread stack size by increasing the value of
     <literal>thread_stack</literal> at server startup. See

@@ -121,10 +112,35 @@
   </para>
 
   <para>
-    Stored functions cannot be recursive. See
-    <xref linkend="routine-restrictions"/>.
+    <emphasis role="bold">Additional resources</emphasis>
   </para>
 
+  <itemizedlist>
+
+    <listitem>
+      <para>
+        Binary logging for stored routines takes place as described in
+        <xref linkend="stored-procedure-logging"/>.
+      </para>
+    </listitem>
+
+    <listitem>
+      <para>
+        Answers to some questions that are commonly asked regarding
+        stored routines in MySQL can be found in
+        <xref linkend="faqs-stored-procs"/>.
+      </para>
+    </listitem>
+
+    <listitem>
+      <para>
+        Discussion of restrictions on use of stored routines is given in
+        <xref linkend="routine-restrictions"/>.
+      </para>
+    </listitem>
+
+  </itemizedlist>
+
   <section id="stored-procedure-privileges">
 
     <title>Stored Routines and the Grant Tables</title>

@@ -1222,7 +1238,7 @@
       <remark role="help-description-end"/>
 
       <para>
-        The optional <literal>[NOT] ATOMIC</literal> clause is not yet
+        The optional <literal>[NOT] ATOMIC</literal> clause is not
         supported. This means that no transactional savepoint is set at
         the start of the instruction block and the
         <literal>BEGIN</literal> clause used in this context has no

@@ -1575,7 +1591,7 @@
           terminates for the <literal>BEGIN ... END</literal> compound
           statement in which the handler is declared. (This is true even
           if the condition occurs in an inner block.) The
-          <literal>UNDO</literal> handler type statement is not yet
+          <literal>UNDO</literal> handler type statement is not
           supported.
         </para>
 

@@ -1806,7 +1822,7 @@
 
       <para>
         Cursors are supported inside stored procedures and functions and
-        triggers. The syntax is as in embedded SQL. Cursors currently
+        triggers. The syntax is as in embedded SQL. Cursors in MySQL
         have these properties:
       </para>
 

@@ -2032,7 +2048,7 @@
       </para>
 
       <para>
-        <literal>FOR</literal> loops are not currently supported.
+        <literal>FOR</literal> loops are not supported.
       </para>
 
       <section id="if-statement">


Modified: trunk/refman-6.0/stored-procedures.xml
===================================================================
--- trunk/refman-6.0/stored-procedures.xml	2008-09-08 19:17:59 UTC (rev 11735)
+++ trunk/refman-6.0/stored-procedures.xml	2008-09-08 19:47:31 UTC (rev 11736)
Changed blocks: 7, Lines Added: 37, Lines Deleted: 21; 4145 bytes

@@ -26,12 +26,6 @@
     the stored procedure instead.
   </para>
 
-  <para>
-    Answers to some questions that are commonly asked regarding stored
-    routines in MySQL can be found in
-    <xref linkend="faqs-stored-procs"/>.
-  </para>
-
   <formalpara role="mnmas">
 
     <title>MySQL Enterprise</title>

@@ -98,22 +92,19 @@
   <para>
     The MySQL implementation of stored routines is still in progress.
     All syntax described in this chapter is supported and any
-    limitations and extensions are documented where appropriate. Further
-    discussion of restrictions on use of stored routines is given in
-    <xref linkend="routine-restrictions"/>.
+    limitations and extensions are documented where appropriate.
   </para>
 
   <para>
-    Binary logging for stored routines takes place as described in
-    <xref linkend="stored-procedure-logging"/>.
+    Stored functions cannot be recursive.
   </para>
 
   <para>
-    Recursive stored procedures are disabled by default, but can be
-    enabled on the server by setting the
+    Recursion in stored procedures is allowed but disabled by default.
+    To enable recursion, set the
     <literal>max_sp_recursion_depth</literal> server system variable to
-    a nonzero value. Stored procedure recursion increases the demand on
-    thread stack space. If you increase the value of
+    a value greater than zero. Stored procedure recursion increases the
+    demand on thread stack space. If you increase the value of
     <literal>max_sp_recursion_depth</literal>, it may be necessary to
     increase thread stack size by increasing the value of
     <literal>thread_stack</literal> at server startup. See

@@ -121,10 +112,35 @@
   </para>
 
   <para>
-    Stored functions cannot be recursive. See
-    <xref linkend="routine-restrictions"/>.
+    <emphasis role="bold">Additional resources</emphasis>
   </para>
 
+  <itemizedlist>
+
+    <listitem>
+      <para>
+        Binary logging for stored routines takes place as described in
+        <xref linkend="stored-procedure-logging"/>.
+      </para>
+    </listitem>
+
+    <listitem>
+      <para>
+        Answers to some questions that are commonly asked regarding
+        stored routines in MySQL can be found in
+        <xref linkend="faqs-stored-procs"/>.
+      </para>
+    </listitem>
+
+    <listitem>
+      <para>
+        Discussion of restrictions on use of stored routines is given in
+        <xref linkend="routine-restrictions"/>.
+      </para>
+    </listitem>
+
+  </itemizedlist>
+
   <section id="stored-procedure-privileges">
 
     <title>Stored Routines and the Grant Tables</title>

@@ -1220,7 +1236,7 @@
       <remark role="help-description-end"/>
 
       <para>
-        The optional <literal>[NOT] ATOMIC</literal> clause is not yet
+        The optional <literal>[NOT] ATOMIC</literal> clause is not
         supported. This means that no transactional savepoint is set at
         the start of the instruction block and the
         <literal>BEGIN</literal> clause used in this context has no

@@ -1573,7 +1589,7 @@
           terminates for the <literal>BEGIN ... END</literal> compound
           statement in which the handler is declared. (This is true even
           if the condition occurs in an inner block.) The
-          <literal>UNDO</literal> handler type statement is not yet
+          <literal>UNDO</literal> handler type statement is not
           supported.
         </para>
 

@@ -1804,7 +1820,7 @@
 
       <para>
         Cursors are supported inside stored procedures and functions and
-        triggers. The syntax is as in embedded SQL. Cursors currently
+        triggers. The syntax is as in embedded SQL. Cursors in MySQL
         have these properties:
       </para>
 

@@ -2030,7 +2046,7 @@
       </para>
 
       <para>
-        <literal>FOR</literal> loops are not currently supported.
+        <literal>FOR</literal> loops are not supported.
       </para>
 
       <section id="if-statement">