svn commit - mysqldoc@docsrva: r5671 - in trunk: . refman-4.1 refman-5.0 refman-5.1

[paul]

Author: paul
Date: 2007-04-01 01:38:26 +0200 (Sun, 01 Apr 2007)
New Revision: 5671

Log:
 r18430@frost:  paul | 2007-03-31 18:38:11 -0500
 Document bugfixes:
 Bug#23736
 Bug#25492
 Bug#26079
 Bug#26503
 Bug#26625
 Bug#26996
 Bug#27036
 Bug#27231
 Bug#27378


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

Property changes on: trunk
___________________________________________________________________
Name: svk:merge
   - 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:22522
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:18424
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:14593
   + 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:22522
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:18430
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:14593


Modified: trunk/refman-4.1/news-4.1.xml
===================================================================
--- trunk/refman-4.1/news-4.1.xml	2007-03-31 18:09:04 UTC (rev 5670)
+++ trunk/refman-4.1/news-4.1.xml	2007-03-31 23:38:26 UTC (rev 5671)
Changed blocks: 1, Lines Added: 15, Lines Deleted: 0; 862 bytes

@@ -299,6 +299,21 @@
 
       <listitem>
         <para>
+          In a <literal>MEMORY</literal> table, using a
+          <literal>BTREE</literal> index to scan for updatable rows
+          could lead to an infinite loop. (Bug #26996)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          The range optimizer could cause the server to run out of
+          memory. (Bug #26625)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           Difficult repair or optimization operations could cause an
           assertion failure, resulting in a server crash. (Bug #25289)
         </para>


Modified: trunk/refman-5.0/releasenotes-es-5.0.xml
===================================================================
--- trunk/refman-5.0/releasenotes-es-5.0.xml	2007-03-31 18:09:04 UTC (rev 5670)
+++ trunk/refman-5.0/releasenotes-es-5.0.xml	2007-03-31 23:38:26 UTC (rev 5671)
Changed blocks: 3, Lines Added: 38, Lines Deleted: 7; 2209 bytes

@@ -154,6 +154,36 @@
 
       <listitem>
         <para>
+          <literal>mysql_stmt_fetch()</literal> did an invalid memory
+          deallocation when used with the embedded server. (Bug #25492)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          In a <literal>MEMORY</literal> table, using a
+          <literal>BTREE</literal> index to scan for updatable rows
+          could lead to an infinite loop. (Bug #26996)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          The range optimizer could cause the server to run out of
+          memory. (Bug #26625)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          The parser accepted illegal code in SQL exception handlers,
+          leading to a crash at runtime when executing the code. (Bug
+          #26503)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           Difficult repair or optimization operations could cause an
           assertion failure, resulting in a server crash. (Bug #25289)
         </para>

@@ -399,6 +429,14 @@
 
       <listitem>
         <para>
+          <literal>SELECT ... INTO OUTFILE</literal> with a long
+          <literal>FIELDS ENCLOSED BY</literal> value could crash the
+          server. (Bug #27231)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           <literal>DOUBLE</literal> values such as
           <literal>20070202191048.000000</literal> were being treated as
           illegal arguments by <literal>WEEK()</literal>. (Bug #23616)

@@ -1304,13 +1342,6 @@
 
       <listitem>
         <para>
-          <literal>mysql_stmt_fetch()</literal> did an invalid memory
-          deallocation when used with the embedded server. (Bug #25492)
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
           <literal>mysql_kill()</literal> caused a server crash when
           used on an SSL connection. (Bug #25203)
         </para>


Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml	2007-03-31 18:09:04 UTC (rev 5670)
+++ trunk/refman-5.1/news-5.1.xml	2007-03-31 23:38:26 UTC (rev 5671)
Changed blocks: 4, Lines Added: 109, Lines Deleted: 49; 6701 bytes

@@ -91,6 +91,44 @@
 
       <listitem>
         <para>
+          <literal>NDB Cluster</literal>: An
<literal>UPDATE</literal>
+          on the master became a <literal>DELETE</literal> on slaves.
+          (Bug #27378)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>mysql_stmt_fetch()</literal> did an invalid memory
+          deallocation when used with the embedded server. (Bug #25492)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          For <literal>FEDERATED</literal> tables, <literal>SHOW CREATE
+          TABLE</literal> could fail when the table name was longer than
+          the connection name. (Bug #27036)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          In a <literal>MEMORY</literal> table, using a
+          <literal>BTREE</literal> index to scan for updatable rows
+          could lead to an infinite loop. (Bug #26996)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          The range optimizer could cause the server to run out of
+          memory. (Bug #26625)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           <literal>CREATE SERVER</literal>, <literal>DROP
           SERVER</literal>, and <literal>ALTER SERVER</literal> did not
           require any privileges. Now these statements require the

@@ -417,53 +455,14 @@
 
       <listitem>
         <para>
-          Increasing the width of a <literal>DECIMAL</literal> column
-          could cause column values to be changed. (Bug #24558)
+          The parser accepted illegal code in SQL exception handlers,
+          leading to a crash at runtime when executing the code. (Bug
+          #26503)
         </para>
       </listitem>
 
       <listitem>
         <para>
-          <literal>DOUBLE</literal> values such as
-          <literal>20070202191048.000000</literal> were being treated as
-          illegal arguments by <literal>WEEK()</literal>. (Bug #23616)
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
-          Replication between master and slave would infinitely retry
-          binary log transmission where the
-          <option>max_allowed_packet</option> on the master was larger
-          than that on the slave if the size of the transfer was between
-          these two values. (Bug #23775)
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
-          Setting <literal>event_scheduler=1</literal> or
-          <literal>event_scheduler=ON</literal> caused the server to
-          crash if the server had been started with
-          <option>--skip-grant-tables</option>. Starting the server with
-          <option>--skip-grant-tables</option> now causes
-          <literal>event_scheduler</literal> to be set to
-          <literal>DISABLED</literal> automatically, overriding any
-          other value that may have been set. (Bug #26807)
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
-          <literal>SHOW CREATE EVENT</literal> failed to display the
-          <literal>STARTS</literal> and <literal>ENDS</literal>
clauses
-          for an event defined with <literal>STARTS NOW()</literal>,
-          <literal>ENDS NOW()</literal>, or both. (Bug #26429)
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
           <literal>NDB Cluster</literal>: After putting the cluster in
           single user mode from one MySQL server, trying to drop an NDB
           table from a second MySQL server also connected to the cluster

@@ -692,6 +691,74 @@
 
       <listitem>
         <para>
+          Debug builds of <command>mysqlbinlog</command> could fail with
+          a memory error. (Bug #23736)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>SELECT ... INTO OUTFILE</literal> with a long
+          <literal>FIELDS ENCLOSED BY</literal> value could crash the
+          server. (Bug #27231)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          The server could hang during binary log rotation. (Bug #26079)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Increasing the width of a <literal>DECIMAL</literal> column
+          could cause column values to be changed. (Bug #24558)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>DOUBLE</literal> values such as
+          <literal>20070202191048.000000</literal> were being treated as
+          illegal arguments by <literal>WEEK()</literal>. (Bug #23616)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Replication between master and slave would infinitely retry
+          binary log transmission where the
+          <option>max_allowed_packet</option> on the master was larger
+          than that on the slave if the size of the transfer was between
+          these two values. (Bug #23775)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Setting <literal>event_scheduler=1</literal> or
+          <literal>event_scheduler=ON</literal> caused the server to
+          crash if the server had been started with
+          <option>--skip-grant-tables</option>. Starting the server with
+          <option>--skip-grant-tables</option> now causes
+          <literal>event_scheduler</literal> to be set to
+          <literal>DISABLED</literal> automatically, overriding any
+          other value that may have been set. (Bug #26807)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>SHOW CREATE EVENT</literal> failed to display the
+          <literal>STARTS</literal> and <literal>ENDS</literal>
clauses
+          for an event defined with <literal>STARTS NOW()</literal>,
+          <literal>ENDS NOW()</literal>, or both. (Bug #26429)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           Invalid optimization of pushdown conditions for queries where
           an outer join was guaranteed to read only one row from the
           outer table led to results with too few rows. (Bug #26963)

@@ -1956,13 +2023,6 @@
 
       <listitem>
         <para>
-          <literal>mysql_stmt_fetch()</literal> did an invalid memory
-          deallocation when used with the embedded server. (Bug #25492)
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
           <literal>mysql_kill()</literal> caused a server crash when
           used on an SSL connection. (Bug #25203)
         </para>