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

[jon]

Author: jstephens
Date: 2007-02-01 03:08:49 +0100 (Thu, 01 Feb 2007)
New Revision: 4725

Log:

Documenting P1 bugfixes:
  Bug #6774,  Bug #22864, Bug #24117, Bug #24261, Bug #24670,
  Bug #24404, Bug #24490, Bug #24571, Bug #24776, Bug #25172,
  Bug #25219, Bug #25398



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


Modified: trunk/refman-4.1/news-4.1.xml
===================================================================
--- trunk/refman-4.1/news-4.1.xml	2007-02-01 00:05:27 UTC (rev 4724)
+++ trunk/refman-4.1/news-4.1.xml	2007-02-01 02:08:49 UTC (rev 4725)
Changed blocks: 1, Lines Added: 24, Lines Deleted: 0; 1092 bytes

@@ -223,6 +223,30 @@
     </para>
 
     <itemizedlist>
+      
+      <listitem>
+        <para>
+          Certain joins using <literal>Range checked for each
+            record</literal> in the query execution plan could cause the
+          server to crash. (Bug #24776)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          If there was insufficient memory available to
+          <command>mysqld</command>, this could sometimes cause the
+          server to hang during startup. (Bug #24751)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          Optimizations that are legal only for subqueries without
+          tables and <literal>WHERE</literal> conditions were applied
+          for any subquery without tables. (Bug #24670)
+        </para>
+      </listitem>
 
       <listitem>
         <para>


Modified: trunk/refman-5.0/news-5.0.xml
===================================================================
--- trunk/refman-5.0/news-5.0.xml	2007-02-01 00:05:27 UTC (rev 4724)
+++ trunk/refman-5.0/news-5.0.xml	2007-02-01 02:08:49 UTC (rev 4725)
Changed blocks: 2, Lines Added: 17, Lines Deleted: 0; 959 bytes

@@ -3230,6 +3230,15 @@
     </para>
 
     <itemizedlist>
+      
+      <listitem>
+        <para>
+          An invalid <literal>GRANT</literal> statement for which
+          <literal>Ok</literal> was returned on a replication master
+          caused an error on the slave and replication to fail. (Bug
+          #6774) 
+        </para>
+      </listitem>
 
       <listitem>
         <para>

@@ -9888,6 +9897,14 @@
     </para>
 
     <itemizedlist>
+      
+      <listitem>
+        <para>
+          Certain joins using <literal>Range checked for each
+            record</literal> in the query execution plan could cause the
+          server to crash. (Bug #24776)
+        </para>
+      </listitem>
 
       <listitem>
         <para>


Modified: trunk/refman-5.0/releasenotes-es-5.0.xml
===================================================================
--- trunk/refman-5.0/releasenotes-es-5.0.xml	2007-02-01 00:05:27 UTC (rev 4724)
+++ trunk/refman-5.0/releasenotes-es-5.0.xml	2007-02-01 02:08:49 UTC (rev 4725)
Changed blocks: 2, Lines Added: 68, Lines Deleted: 0; 2735 bytes

@@ -106,6 +106,66 @@
     </para>
 
     <itemizedlist>
+      
+      <listitem>
+        <para>
+          An <literal>AFTER UPDATE</literal> trigger on an
+          <literal>InnoDB</literal> table with a composite primary key
+          caused the server to crash. (Bug#25398)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          A query that contained an <literal>EXIST</literal> subquery
+          with a <literal>UNION</literal> over correlated and
+          uncorrelated <literal>SELECT</literal> queries could cause the
+          server to crash. (Bug #25219) 
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          A query with <literal>ORDER BY</literal> and <literal>GROUP
+            BY</literal> clauses where the <literal>ORDER BY</literal>
+          clause had more elements than the <literal>GROUP BY</literal>
+          clause caused a memory overrun leading to a crash of the
+          server. (Bug #25172)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          If there was insufficient memory available to
+          <command>mysqld</command>, this could sometimes cause the
+          server to hang during startup. (Bug #24751)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          If a prepared statement accessed a view, access to the tables
+          listed in the query after that view was checked in the
+          security context of the view. (Bug #24404)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          A query using <literal>WHERE
+            <replaceable>unsigned_column</replaceable> NOT IN
+            ('<replaceable>negative_value</replaceable>')</literal>
+          could cause the server to crash. (Bug #24261)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          A <literal>FETCH</literal> statement using a cursor on a table
+          which was not in the table cache could sometimes cause the
+          server to crash. (Bug #24117) 
+        </para>
+      </listitem>
 
       <listitem>
         <para>

@@ -383,6 +443,14 @@
     </para>
 
     <itemizedlist>
+      
+      <listitem>
+        <para>
+          Optimizations that are legal only for subqueries without
+          tables and <literal>WHERE</literal> conditions were applied
+          for any subquery without tables. (Bug #24670)
+        </para>
+      </listitem>
 
       <listitem>
         <para>


Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml	2007-02-01 00:05:27 UTC (rev 4724)
+++ trunk/refman-5.1/news-5.1.xml	2007-02-01 02:08:49 UTC (rev 4725)
Changed blocks: 3, Lines Added: 104, Lines Deleted: 0; 4295 bytes

@@ -102,6 +102,49 @@
       
       <listitem>
         <para>
+          An <literal>AFTER UPDATE</literal> trigger on an
+          <literal>InnoDB</literal> table with a composite primary key
+          caused the server to crash. (Bug#25398)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          A query that contained an <literal>EXIST</literal> subquery
+          with a <literal>UNION</literal> over correlated and
+          uncorrelated <literal>SELECT</literal> queries could cause the
+          server to crash. (Bug #25219) 
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          A query with <literal>ORDER BY</literal> and <literal>GROUP
+            BY</literal> clauses where the <literal>ORDER BY</literal>
+          clause had more elements than the <literal>GROUP BY</literal>
+          clause caused a memory overrun leading to a crash of the
+          server. (Bug #25172)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          Certain joins using <literal>Range checked for each
+            record</literal> in the query execution plan could cause the
+          server to crash. (Bug #24776)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          If a prepared statement accessed a view, access to the tables
+          listed in the query after that view was checked in the
+          security context of the view. (Bug #24404)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
           A nested query on a partitioned table returned fewer records
           than on the corresponding non-partitioned table, when the
           subquery affected more than one partition. (Bug #24186)

@@ -386,6 +429,58 @@
     </para>
 
     <itemizedlist>
+      
+      <listitem>
+        <para>
+          If there was insufficient memory available to
+          <command>mysqld</command>, this could sometimes cause the
+          server to hang during startup. (Bug #24751)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          Using row-based replication to replicate to a table having at
+          least one extra <literal>BIT</literal> column with a default
+          value on the slave as compared to the master could cause the
+          slave to fail. (Bug #24490)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          Optimizations that are legal only for subqueries without
+          tables and <literal>WHERE</literal> conditions were applied
+          for any subquery without tables. (Bug #24670)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          A query using <literal>WHERE
+            <replaceable>unsigned_column</replaceable> NOT IN
+            ('<replaceable>negative_value</replaceable>')</literal>
+          could cause the server to crash. (Bug #24261)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          A <literal>FETCH</literal> statement using a cursor on a table
+          which was not in the table cache could sometimes cause the
+          server to crash. (Bug #24117) 
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>CREATE TABLE ... SELECT</literal> statements were not
+          rolled back correctly. As part of the fix, such a statement
+          now causes an implicit commit before and after it is executed.
+          However, it does not cause a commit when used to create a
+          temporary table. (Bug #22864)
+        </para>
+      </listitem>
 
       <listitem>
         <para>

@@ -4113,6 +4208,15 @@
 REPAIR TABLE <replaceable>tbl_name</replaceable> QUICK;
 </programlisting>
       </listitem>
+      
+      <listitem>
+        <para>
+          An invalid <literal>GRANT</literal> statement for which
+          <literal>Ok</literal> was returned on a replication master
+          caused an error on the slave and replication to fail. (Bug
+          #6774) 
+        </para>
+        </listitem>
 
       <listitem>
         <para>


Modified: trunk/refman-5.1/sql-syntax.xml
===================================================================
--- trunk/refman-5.1/sql-syntax.xml	2007-02-01 00:05:27 UTC (rev 4724)
+++ trunk/refman-5.1/sql-syntax.xml	2007-02-01 02:08:49 UTC (rev 4725)
Changed blocks: 1, Lines Added: 9, Lines Deleted: 0; 789 bytes

@@ -12667,6 +12667,15 @@
             <literal>CREATE INDEX</literal>, which do cause a commit.)
           </para>
         </listitem>
+        
+        <listitem>          
+          <para>
+            Beginning with MySQL 5.1.15, <literal>CREATE TABLE ...
+              SELECT</literal> causes an implicit commit before and
+            after the statement is executed. However, no commit occurs
+            for <literal>CREATE TEMPORARY TABLE ... SELECT</literal>.  
+          </para>
+        </listitem>
 
         <listitem>
           <para>