List:Commits« Previous MessageNext Message »
From:paul Date:December 18 2005 5:24am
Subject:svn commit - mysqldoc@docsrva: r588 - in trunk: . refman-common
View as plain text  
Author: paul
Date: 2005-12-18 06:24:27 +0100 (Sun, 18 Dec 2005)
New Revision: 588

Log:
 r4895@frost:  paul | 2005-12-17 23:24:02 -0600
 Document bugfixes:
 Bug#12071
 Bug#13108
 Bug#13778
 Bug#15406


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


Property changes on: trunk
___________________________________________________________________
Name: svk:merge
   - b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:4893
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:1694
   + b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:4895
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:1694

Modified: trunk/refman-common/news-4.1.xml
===================================================================
--- trunk/refman-common/news-4.1.xml	2005-12-18 05:19:53 UTC (rev 587)
+++ trunk/refman-common/news-4.1.xml	2005-12-18 05:24:27 UTC (rev 588)
@@ -179,17 +179,35 @@
     </para>
 
     <itemizedlist>
-      
+
       <listitem>
         <para>
+          A race condition when creating temporary files caused a
+          deadlock on Windows with threads in <literal>Opening
+          tables</literal> or <literal>Waiting for table</literal>
+          states. (Bug #12071)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>InnoDB</literal>: If
+          <literal>FOREIGN_KEY_CHECKS</literal> was 0,
+          <literal>InnoDB</literal> allowed inconsistent foreign keys to
+          be created. (Bug #13778)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           <literal>NDB Cluster</literal>: A memory leak occurred when
           performing ordered index scans using indexes a columns larger
           than 32 bytes, which would eventually lead to the forced
           shutdown of all <command>mysqld</command> server processes
-          used with the cluster. (Bug #13078) 
+          used with the cluster. (Bug #13078)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           <literal>NDB Cluster</literal>: Under some circumstances, it
@@ -197,7 +215,7 @@
           shutdown. (Bug #15632)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           <literal>NDB Cluster</literal>: If an abort by the Transaction
@@ -206,7 +224,7 @@
           prematurely. (Bug #15685)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           <literal>NDB Cluster</literal>: A node which failed during

Modified: trunk/refman-common/news-5.0.xml
===================================================================
--- trunk/refman-common/news-5.0.xml	2005-12-18 05:19:53 UTC (rev 587)
+++ trunk/refman-common/news-5.0.xml	2005-12-18 05:24:27 UTC (rev 588)
@@ -205,15 +205,33 @@
     </para>
 
     <itemizedlist>
-      
+
       <listitem>
         <para>
+          A race condition when creating temporary files caused a
+          deadlock on Windows with threads in <literal>Opening
+          tables</literal> or <literal>Waiting for table</literal>
+          states. (Bug #12071)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>InnoDB</literal>: If
+          <literal>FOREIGN_KEY_CHECKS</literal> was 0,
+          <literal>InnoDB</literal> allowed inconsistent foreign keys to
+          be created. (Bug #13778)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           <literal>NDB Cluster</literal>: Under some circumstances, it
           was possible for a restarting node to undergo a forced
           shutdown. (Bug #15632)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           <literal>NDB Cluster</literal>: If an abort by the Transaction
@@ -222,7 +240,7 @@
           prematurely. (Bug #15685)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           <literal>NDB Cluster</literal>: The
@@ -231,7 +249,7 @@
           Bug #15401.)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           <literal>NDB Cluster</literal>: A node which failed during
@@ -239,7 +257,7 @@
           list of active nodes. (Bug #15587)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           Resolution of the argument to the <literal>VALUES()</literal>
@@ -312,17 +330,17 @@
     </para>
 
     <itemizedlist>
-      
+
       <listitem>
         <para>
-          <literal>NDB Cluster</literal>: Using <literal>ORDER
-            BY <replaceable>primary_key_column</replaceable></literal>
-          when selecting from a table having the primary key on a
+          <literal>NDB Cluster</literal>: Using <literal>ORDER BY
+          <replaceable>primary_key_column</replaceable></literal> when
+          selecting from a table having the primary key on a
           <literal>VARCHAR</literal> column caused a forced shutdown of
           the cluster. (Bug #14828, Bug #15240, Bug #15682, Bug #15517)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           <literal>NDB Cluster</literal>: Under certain circumstances,
@@ -1015,14 +1033,14 @@
     </para>
 
     <itemizedlist>
-      
+
       <listitem>
         <para>
           <literal>NDB Cluster</literal>: A memory leak occurred when
           performing ordered index scans using indexes a columns larger
           than 32 bytes, which would eventually lead to the forced
           shutdown of all <command>mysqld</command> server processes
-          used with the cluster. (Bug #13078) 
+          used with the cluster. (Bug #13078)
         </para>
       </listitem>
 
@@ -2700,6 +2718,14 @@
 
       <listitem>
         <para>
+          The <literal>FEDERATED</literal> storage engine does not
+          support <literal>ALTER TABLE</literal>, but no appropriate
+          error message was issued. (Bug #13108)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           <command>mysqldump</command> did not dump triggers properly.
           (Bug #12597)
         </para>

Modified: trunk/refman-common/news-5.1.xml
===================================================================
--- trunk/refman-common/news-5.1.xml	2005-12-18 05:19:53 UTC (rev 587)
+++ trunk/refman-common/news-5.1.xml	2005-12-18 05:24:27 UTC (rev 588)
@@ -89,12 +89,20 @@
     </para>
 
     <itemizedlist>
-      
+
       <listitem>
         <para>
-          <literal>NDB Cluster</literal>: Using <literal>ORDER
-            BY <replaceable>primary_key_column</replaceable></literal>
-          when selecting from a table having the primary key on a
+          The <literal>BLACKHOLE</literal> storage engine did not handle
+          transactions properly: Rolled-back transactions were written
+          to the binary log. Now they ae not. (Bug #15406)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: Using <literal>ORDER BY
+          <replaceable>primary_key_column</replaceable></literal> when
+          selecting from a table having the primary key on a
           <literal>VARCHAR</literal> column caused a forced shutdown of
           the cluster. (Bug #14828, Bug #15240, Bug #15682, Bug #15517)
         </para>

Thread
svn commit - mysqldoc@docsrva: r588 - in trunk: . refman-commonpaul18 Dec