List:Commits« Previous MessageNext Message »
From:jon Date:August 15 2006 1:16pm
Subject:svn commit - mysqldoc@docsrva: r3023 - trunk/refman-common
View as plain text  
Author: jstephens
Date: 2006-08-15 15:16:22 +0200 (Tue, 15 Aug 2006)
New Revision: 3023

Log:

Documenting bugfixes:

  Bug #16211, Bug #16676, Bug #17608,
  Bug #18630, Bug #19207, Bug #19399,
  Bug #19939, Bug #20438, Bug #21013



Modified:
   trunk/refman-common/news-4.1.xml
   trunk/refman-common/news-5.0.xml
   trunk/refman-common/news-5.1.xml


Modified: trunk/refman-common/news-4.1.xml
===================================================================
--- trunk/refman-common/news-4.1.xml	2006-08-15 11:16:23 UTC (rev 3022)
+++ trunk/refman-common/news-4.1.xml	2006-08-15 13:16:22 UTC (rev 3023)
Changed blocks: 1, Lines Added: 8, Lines Deleted: 0; 633 bytes

@@ -472,6 +472,14 @@
           Hammers from the Debian Team for notifying us of it.
         </para>
       </listitem>
+      
+      <listitem>
+        <para>
+          Repeated <literal>DROP TABLE</literal> statements in a stored
+          procedure could sometimes cause the server to crash. (Bug
+          #19399) 
+        </para>
+      </listitem>
 
       <listitem>
         <para>


Modified: trunk/refman-common/news-5.0.xml
===================================================================
--- trunk/refman-common/news-5.0.xml	2006-08-15 11:16:23 UTC (rev 3022)
+++ trunk/refman-common/news-5.0.xml	2006-08-15 13:16:22 UTC (rev 3023)
Changed blocks: 1, Lines Added: 72, Lines Deleted: 0; 3088 bytes

@@ -305,9 +305,81 @@
           first by the case of one or more letters. (Bug #17647)
         </para>
       </listitem>
+      
+      <listitem>
+        <para>
+          <emphasis role="bold">Security fix</emphasis>: A stored
+          routine created by one user and then made accessible to
+          a different user using <literal>GRANT EXECUTE</literal> could
+          be executed by that user with the privileges of the routine's
+          definer. (Bug #18630) 
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          Stored procedures did not use the character set defined for
+          the database in which they were created. (Bug #16676)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>CREATE PROCEDURE</literal>, <literal>CREATE
+            FUNTION</literal>, <literal>CREATE TRIGGER</literal>, and
+          <literal>CREATE VIEW</literal> statements containing
+          multi-line comments (<literal>/* ... */</literal>) could not
+          be replicated. (Bug #20438)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          The final parenthesis of a <literal>CREATE INDEX</literal>
+          statement occurring in a stored procedure was omitted from the
+          binary log when the stored procedure was called. (Bug #19207)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          Attempting to insert a string of greater than 4096 bytes into
+          a <literal>FEDERATED</literal> table resulted in the error
+          <errortext>ERROR 1296 (HY000) at line 2: Got error 10000
+            'Error on remote system: 1054: Unknown column
+            '<replaceable>string-value</replaceable>' from
+            FEDERATED</errortext>. This error was raised regardless of
+          the type of column involved (<literal>VARCHAR</literal>,
+          <literal>TEXT</literal>, and so on.) (Bug #17608)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          Performance during an import on a table with a trigger that
+          called a stored procedure was severely degraded. This issue
+          first arose in MySQL 5.0.18. (Bug #21013)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          Repeated <literal>DROP TABLE</literal> statements in a stored
+          procedure could sometimes cause the server to crash. (Bug
+          #19399) 
+        </para>
+      </listitem>
 
+      
       <listitem>
         <para>
+          The value returned by a stored function returning a string
+          value was not of the declared character set. (Bug #16211)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           For <command>mysql</command>, escaping with backslash
           sometimes did not work. (Bug #20103)
         </para>


Modified: trunk/refman-common/news-5.1.xml
===================================================================
--- trunk/refman-common/news-5.1.xml	2006-08-15 11:16:23 UTC (rev 3022)
+++ trunk/refman-common/news-5.1.xml	2006-08-15 13:16:22 UTC (rev 3023)
Changed blocks: 3, Lines Added: 78, Lines Deleted: 0; 3446 bytes

@@ -530,6 +530,16 @@
           <literal>MERGE</literal> storage engine. (Bug #15195)
         </para>
       </listitem>
+      
+      <listitem>
+        <para>
+          <emphasis role="bold">Security fix</emphasis>: A stored
+          routine created by one user and then made accessible to
+          a different user using <literal>GRANT EXECUTE</literal> could
+          be executed by that user with the privileges of the routine's
+          definer. (Bug #18630) 
+        </para>
+      </listitem>
 
       <listitem>
         <para>

@@ -551,7 +561,68 @@
 REPAIR TABLE <replaceable>tbl_name</replaceable> QUICK;
 </programlisting>
       </listitem>
+      
+      <listitem>
+        <para>
+          <literal>AUTHORS</literal> was not treated as a reserved
+          word. (Bug #19939)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          Stored procedures did not use the character set defined for
+          the database in which they were created. (Bug #16676)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>CREATE PROCEDURE</literal>, <literal>CREATE
+            FUNTION</literal>, <literal>CREATE TRIGGER</literal>, and
+          <literal>CREATE VIEW</literal> statements containing
+          multi-line comments (<literal>/* ... */</literal>) could not
+          be replicated. (Bug #20438)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          The final parenthesis of a <literal>CREATE INDEX</literal>
+          statement occurring in a stored procedure was omitted from the
+          binary log when the stored procedure was called. (Bug #19207)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          Attempting to insert a string of greater than 4096 bytes into
+          a <literal>FEDERATED</literal> table resulted in the error
+          <errortext>ERROR 1296 (HY000) at line 2: Got error 10000
+            'Error on remote system: 1054: Unknown column
+            '<replaceable>string-value</replaceable>' from
+            FEDERATED</errortext>. This error was raised regardless of
+          the type of column involved (<literal>VARCHAR</literal>,
+          <literal>TEXT</literal>, and so on.) (Bug #17608)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          Performance during an import on a table with a trigger that
+          called a stored procedure was severely degraded. (Bug #21013)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          Repeated <literal>DROP TABLE</literal> statements in a stored
+          procedure could sometimes cause the server to crash. (Bug
+          #19399) 
+        </para>
+      </listitem>
 
+
       <listitem>
         <para>
           On 64-bit Windows, a missing table generated error 1017, not

@@ -568,6 +639,13 @@
           conditions so as to be more informative. (Bug #10946)
         </para>
       </listitem>
+      
+      <listitem>
+        <para>
+          The value returned by a stored function returning a string
+          value was not of the declared character set. (Bug #16211)
+        </para>
+      </listitem>
 
       <listitem>
         <para>


Thread
svn commit - mysqldoc@docsrva: r3023 - trunk/refman-commonjon15 Aug