List:Commits« Previous MessageNext Message »
From:jon Date:November 4 2006 4:01am
Subject:svn commit - mysqldoc@docsrva: r3837 - in trunk: refman-4.1 refman-5.0 refman-5.1
View as plain text  
Author: jstephens
Date: 2006-11-04 05:01:07 +0100 (Sat, 04 Nov 2006)
New Revision: 3837

Log:

Documenting fix/behaviour change for Cluster (ref. Bug #21378)



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


Modified: trunk/refman-4.1/news-4.1.xml
===================================================================
--- trunk/refman-4.1/news-4.1.xml	2006-11-03 15:00:49 UTC (rev 3836)
+++ trunk/refman-4.1/news-4.1.xml	2006-11-04 04:01:07 UTC (rev 3837)
Changed blocks: 1, Lines Added: 12, Lines Deleted: 0; 1006 bytes

@@ -718,6 +718,18 @@
       
       <listitem>
         <para>
+          <literal>NDB Cluster</literal>: Attempting to create an
+          <literal>NDB</literal> table on a MySQL with an existing
+          non-Cluster table with the same name in the same database
+          could result in data loss or corruption. MySQL now issues a
+          warning when a <literal>SHOW TABLES</literal> or other
+          statement causing table discovery finds such a table. (Bug
+          #21378)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
           <literal>NDB Cluster</literal> (NDB API): Attempting to read a
           nonexistent tuple using <literal>Commit</literal> mode for
           <literal>NdbTransaction::execute()</literal> caused node


Modified: trunk/refman-5.0/releasenotes-es-5.0.xml
===================================================================
--- trunk/refman-5.0/releasenotes-es-5.0.xml	2006-11-03 15:00:49 UTC (rev 3836)
+++ trunk/refman-5.0/releasenotes-es-5.0.xml	2006-11-04 04:01:07 UTC (rev 3837)
Changed blocks: 1, Lines Added: 13, Lines Deleted: 1; 1050 bytes

@@ -84,10 +84,22 @@
     </para>
 
     <itemizedlist>
-
+      
       <listitem>
         <remark role="cluster-tagged-5.0.29-begin"/>
+        
+        <para>
+          <literal>NDB Cluster</literal>: Attempting to create an
+          <literal>NDB</literal> table on a MySQL with an existing
+          non-Cluster table with the same name in the same database
+          could result in data loss or corruption. MySQL now issues a
+          warning when a <literal>SHOW TABLES</literal> or other
+          statement causing table discovery finds such a table. (Bug
+          #21378)
+        </para>
+      </listitem>
 
+      <listitem>
         <para>
           <literal>NDB Cluster</literal> (NDB API): Inacivity timeouts
           for scans were not correctly handled. (Bug #23107)


Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml	2006-11-03 15:00:49 UTC (rev 3836)
+++ trunk/refman-5.1/news-5.1.xml	2006-11-04 04:01:07 UTC (rev 3837)
Changed blocks: 1, Lines Added: 12, Lines Deleted: 0; 915 bytes

@@ -2228,6 +2228,18 @@
           to crash. (Bug #21210)
         </para>
       </listitem>
+        
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: Attempting to create an
+          <literal>NDB</literal> table on a MySQL with an existing
+          non-Cluster table with the same name in the same database
+          could result in data loss or corruption. Now, if such a table
+          is encountered during autodiscovery, a warning is written to
+          the error log of the affected <command>mysqld</command>, and
+          the local table is overwritten. (Bug #21378)
+        </para>
+      </listitem>
       
       <listitem>
         <para>


Thread
svn commit - mysqldoc@docsrva: r3837 - in trunk: refman-4.1 refman-5.0 refman-5.1jon4 Nov