svn commit - mysqldoc@docsrva: r5261 - in trunk: refman-5.0 refman-5.1

[jon]

Author: jstephens
Date: 2007-03-09 04:45:35 +0100 (Fri, 09 Mar 2007)
New Revision: 5261

Log:

Documenting Stored Routines bugfixes:
  
  Bug #8407, Bug #12976, Bug #18914, Bug #22580, Bug #25345



Modified:
   trunk/refman-5.0/releasenotes-es-5.0.xml
   trunk/refman-5.1/news-5.1.xml


Modified: trunk/refman-5.0/releasenotes-es-5.0.xml
===================================================================
--- trunk/refman-5.0/releasenotes-es-5.0.xml	2007-03-09 02:05:40 UTC (rev 5260)
+++ trunk/refman-5.0/releasenotes-es-5.0.xml	2007-03-09 03:45:35 UTC (rev 5261)
Changed blocks: 1, Lines Added: 48, Lines Deleted: 0; 2341 bytes

@@ -139,6 +139,54 @@
           <literal>AUTO_INCREMENT</literal> column. (Bug #21033)
         </para>
       </listitem>
+      
+      <listitem>
+        <para>
+          A stored procedure that made use of cursors failed when the
+          procedure was invoked from a stored function. (Bug #15345)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          When nesting stored procedures within a trigger on a table, a
+          false dependency error was thrown when one of the nested
+          procedures contained a <literal>DROP TABLE</literal> statement.
(Bug #22580)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          When attempting to call a stored procedure creating a table
+          from a trigger on a table <literal>tbl</literal> in a database
+          <literal>db</literal>, the trigger failed with
+          <errortext>ERROR 1146 (42S02): Table 'db.tbl' doesn't
+            exist</errortext>. However, the actual reason that such a trigger fails
is due to
+          the fact that <literal>CREATE TABLE</literal> causes an
+          implicit <literal>COMMIT</literal>, and so a trigger cannot
+          invoke a stored routine containing this statement. A trigger
+          which does so now fails with <errortext>ERROR 1422 (HY000):
+            Explicit or implicit commit is not allowed in stored
+            function or trigger</errortext>, which makes clear the reason for
+          the trigger's failure. (Bug #18914) 
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          Local variables in stored routines or triggers, when declared
+          as the <literal>BIT</literal> type, were interpreted as strings.
+          (Bug #12976)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          When a stored routine attempted to execute a statement
+          accessing a nonexistent table, the error was not caught by the
+          routine's exception handler. (Bug #8407)
+        </para>
+      </listitem>
 
       <listitem>
         <para>


Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml	2007-03-09 02:05:40 UTC (rev 5260)
+++ trunk/refman-5.1/news-5.1.xml	2007-03-09 03:45:35 UTC (rev 5261)
Changed blocks: 1, Lines Added: 48, Lines Deleted: 0; 2303 bytes

@@ -131,6 +131,54 @@
           and thus grow to unreasonable sizes. (Bug #26720)
         </para>
       </listitem>
+      
+      <listitem>
+        <para>
+          A stored procedure that made use of cursors failed when the
+          procedure was invoked from a stored function. (Bug #15345)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          When nesting stored procedures within a trigger on a table, a
+          false dependency error was thrown when one of the nested
+          procedures contained a <literal>DROP TABLE</literal> statement.
(Bug #22580)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          When attempting to call a stored procedure creating a table
+          from a trigger on a table <literal>tbl</literal> in a database
+          <literal>db</literal>, the trigger failed with
+          <errortext>ERROR 1146 (42S02): Table 'db.tbl' doesn't
+            exist</errortext>. However, the actual reason that such a trigger fails
is due to
+          the fact that <literal>CREATE TABLE</literal> causes an
+          implicit <literal>COMMIT</literal>, and so a trigger cannot
+          invoke a stored routine containing this statement. A trigger
+          which does so now fails with <errortext>ERROR 1422 (HY000):
+            Explicit or implicit commit is not allowed in stored
+            function or trigger</errortext>, which makes clear the reason for
+          the trigger's failure. (Bug #18914) 
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          Local variables in stored routines or triggers, when declared
+          as the <literal>BIT</literal> type, were interpreted as strings.
+          (Bug #12976)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          When a stored routine attempted to execute a statement
+          accessing a nonexistent table, the error was not caught by the
+          routine's exception handler. (Bug #8407)
+        </para>
+      </listitem>
 
       <listitem>
         <para>