List:Commits« Previous MessageNext Message »
From:paul Date:June 20 2006 8:01pm
Subject:svn commit - mysqldoc@docsrva: r2446 - in trunk: . refman-common
View as plain text  
Author: paul
Date: 2006-06-20 22:01:38 +0200 (Tue, 20 Jun 2006)
New Revision: 2446

Log:
 r11528@frost:  paul | 2006-06-20 14:52:35 -0500
 Document Bug#20542, Bug#20551.


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
   - 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:10739
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:11523
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:7663
   + 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:10739
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:11528
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:7663

Modified: trunk/refman-common/news-4.1.xml
===================================================================
--- trunk/refman-common/news-4.1.xml	2006-06-20 20:01:19 UTC (rev 2445)
+++ trunk/refman-common/news-4.1.xml	2006-06-20 20:01:38 UTC (rev 2446)
@@ -200,23 +200,23 @@
     </para>
 
     <itemizedlist>
-      
+
       <listitem>
         <para>
           <literal>NDB Cluster</literal>: <literal>LOAD DATA
-            LOCAL</literal> failed to ignore duplicate keys in Cluster
-          tables. (Bug #19496) 
+          LOCAL</literal> failed to ignore duplicate keys in Cluster
+          tables. (Bug #19496)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
-          <literal>NDB Cluster</literal> (Disk Data): Repeated <literal>CREATE</literal> -
-          <literal>INSERT</literal> - <literal>DROP</literal> operations
-          on Disk Data tables could cause the MySQL table definition
-          cache to become corrupt, so that some
-          <command>mysqld</command> processes could access table
-          information but others could not. (Bug #18595)  
+          <literal>NDB Cluster</literal> (Disk Data): Repeated
+          <literal>CREATE</literal> - <literal>INSERT</literal> -
+          <literal>DROP</literal> operations on Disk Data tables could
+          cause the MySQL table definition cache to become corrupt, so
+          that some <command>mysqld</command> processes could access
+          table information but others could not. (Bug #18595)
         </para>
       </listitem>
 
@@ -256,6 +256,24 @@
 
       <listitem>
         <para>
+          The <filename>fill_help_tables.sql</filename> file did not
+          load properly if the <literal>ANSI_QUOTES</literal> SQL mode
+          was enabled. (Bug #20542)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          The <filename>fill_help_tables.sql</filename> file did not
+          contain a <literal>SET NAMES 'utf8'</literal> statement to
+          indicate its encoding. This caused problems for some settings
+          of the MySQL character set such as <literal>big5</literal>.
+          (Bug #20551)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           The MySQL server startup script
           <command>/etc/init.d/mysql</command> (created from
           <command>mysql.server</command>) is now marked to ensure that

Modified: trunk/refman-common/news-5.0.xml
===================================================================
--- trunk/refman-common/news-5.0.xml	2006-06-20 20:01:19 UTC (rev 2445)
+++ trunk/refman-common/news-5.0.xml	2006-06-20 20:01:38 UTC (rev 2446)
@@ -332,7 +332,7 @@
     </para>
 
     <itemizedlist>
-      
+
       <listitem>
         <para>
           <literal>NDB Cluster</literal>: An internal formatting error
@@ -340,54 +340,54 @@
           (Bug #20016)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           <literal>NDB Cluster</literal>: Running management client
           commands while <command>mgmd</command> was in the process of
           disconnecting could cause the management server to fail. (Bug
-          #19932) 
+          #19932)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           <literal>NDB Cluster</literal> (NDBAPI): Update operations on
-          blobs were not checked for illegal operations.          
+          blobs were not checked for illegal operations.
         </para>
-        
+
         <para>
-          <emphasis role="bold">Note</emphasis>: Read locks with blob update
-          operations are now upgraded from read committed to read
+          <emphasis role="bold">Note</emphasis>: Read locks with blob
+          update operations are now upgraded from read committed to read
           shared.
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           <literal>NDB Cluster</literal>: The management client
-          <literal>ALL STOP</literal> command shut down <command>mgmd</command>
-          processes (as well as <command>ndbd</command> processes). (Bug
-          #18966) 
+          <literal>ALL STOP</literal> command shut down
+          <command>mgmd</command> processes (as well as
+          <command>ndbd</command> processes). (Bug #18966)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           <literal>NDB Cluster</literal>: <literal>LOAD DATA
-            LOCAL</literal> failed to ignore duplicate keys in Cluster
-          tables. (Bug #19496) 
+          LOCAL</literal> failed to ignore duplicate keys in Cluster
+          tables. (Bug #19496)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
-          <literal>NDB Cluster</literal> (Disk Data): Repeated <literal>CREATE</literal> -
-          <literal>INSERT</literal> - <literal>DROP</literal> operations
-          on Disk Data tables could cause the MySQL table definition
-          cache to become corrupt, so that some
-          <command>mysqld</command> processes could access table
-          information but others could not. (Bug #18595)  
+          <literal>NDB Cluster</literal> (Disk Data): Repeated
+          <literal>CREATE</literal> - <literal>INSERT</literal> -
+          <literal>DROP</literal> operations on Disk Data tables could
+          cause the MySQL table definition cache to become corrupt, so
+          that some <command>mysqld</command> processes could access
+          table information but others could not. (Bug #18595)
         </para>
       </listitem>
 
@@ -417,6 +417,24 @@
 
       <listitem>
         <para>
+          The <filename>fill_help_tables.sql</filename> file did not
+          load properly if the <literal>ANSI_QUOTES</literal> SQL mode
+          was enabled. (Bug #20542)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          The <filename>fill_help_tables.sql</filename> file did not
+          contain a <literal>SET NAMES 'utf8'</literal> statement to
+          indicate its encoding. This caused problems for some settings
+          of the MySQL character set such as <literal>big5</literal>.
+          (Bug #20551)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           The MySQL server startup script
           <command>/etc/init.d/mysql</command> (created from
           <command>mysql.server</command>) is now marked to ensure that

Modified: trunk/refman-common/news-5.1.xml
===================================================================
--- trunk/refman-common/news-5.1.xml	2006-06-20 20:01:19 UTC (rev 2445)
+++ trunk/refman-common/news-5.1.xml	2006-06-20 20:01:38 UTC (rev 2446)
@@ -137,13 +137,13 @@
           be specified for processing binary log files. (Bug #18351)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           Added the <option>--ndb-use-copying-alter-table</option>
           option to <command>mysqld</command> to provide a fallback in
           case of problems with online <literal>ALTER TABLE</literal>
-          operations on <literal>NDBCluster</literal> tables.     
+          operations on <literal>NDBCluster</literal> tables.
         </para>
       </listitem>
 
@@ -167,26 +167,26 @@
     </para>
 
     <itemizedlist>
-      
+
       <listitem>
         <para>
           Following a failed attempt to add an index to an
           <literal>ARCHIVE</literal> table, it was no longer possible to
           drop the database in which the table had been created. (Bug
-          #17310) 
+          #17310)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           Using <literal>ALTER TABLE ... ENGINE =
-            <replaceable>x</replaceable></literal>, where
+          <replaceable>x</replaceable></literal>, where
           <replaceable>x</replaceable> was not a storage engine
           supported by the server, would cause <command>mysqld</command>
           to crash. (Bug #20397)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           <literal>NDB Cluster</literal> (Replication): A node failure
@@ -195,18 +195,18 @@
           <literal>BLOB</literal>s to crash.
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           <literal>NDB Cluster</literal> (Disk Data):
           <literal>INFORMATION_SCHEMA.FILES</literal> records for
-          <literal>UNDO</literal> files showed incorrect values in the 
+          <literal>UNDO</literal> files showed incorrect values in the
           <literal>EXTENT_SIZE</literal>,
           <literal>FREE_EXTENTS</literal>, and
           <literal>TOTAL_EXTENTS</literal> columns. (Bug #20073)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           <literal>NDB Cluster</literal>: An internal formatting error
@@ -214,38 +214,38 @@
           (Bug #20016)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           <literal>NDB Cluster</literal>: Running management client
           commands while <command>mgmd</command> was in the process of
           disconnecting could cause the management server to fail. (Bug
-          #19932) 
+          #19932)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           <literal>NDB Cluster</literal> (NDBAPI): Update operations on
-          blobs were not checked for illegal operations.          
+          blobs were not checked for illegal operations.
         </para>
-        
+
         <para>
-          <emphasis role="bold">Note</emphasis>: Read locks with blob update
-          operations are now upgraded from read committed to read
+          <emphasis role="bold">Note</emphasis>: Read locks with blob
+          update operations are now upgraded from read committed to read
           shared.
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           <literal>NDB Cluster</literal>: The management client
-          <literal>ALL STOP</literal> command shut down <command>mgmd</command>
-          processes (as well as <command>ndbd</command> processes). (Bug
-          #18966) 
+          <literal>ALL STOP</literal> command shut down
+          <command>mgmd</command> processes (as well as
+          <command>ndbd</command> processes). (Bug #18966)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           Defining a table partitioned by <literal>LIST</literal> with a
@@ -255,7 +255,7 @@
           partitioning key with a constant. (Bug #19801 / Bug #20268)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           Values greater than 2 gigabytes used in the VALUES LESS THAN
@@ -263,7 +263,7 @@
           negative numbers. (Bug #16002)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           <literal>NDB Cluster</literal>: Renaming of table columns was
@@ -271,7 +271,7 @@
           tables. (Bug #20456)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           <literal>NDB Cluster</literal>: Under some circumstances,
@@ -280,7 +280,7 @@
           to the same cluster. (Bug #19770)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           <literal>NDB Cluster</literal> (Replication): One or more of
@@ -290,28 +290,46 @@
           slave clusters to high loads. (Bug #19768)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           <literal>NDB Cluster</literal>: <literal>LOAD DATA
-            LOCAL</literal> failed to ignore duplicate keys in Cluster
-          tables. (Bug #19496) 
+          LOCAL</literal> failed to ignore duplicate keys in Cluster
+          tables. (Bug #19496)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
-          <literal>NDB Cluster</literal> (Disk Data): Repeated <literal>CREATE</literal> -
-          <literal>INSERT</literal> - <literal>DROP</literal> operations
-          on Disk Data tables could cause the MySQL table definition
-          cache to become corrupt, so that some
-          <command>mysqld</command> processes could access table
-          information but others could not. (Bug #18595)  
+          <literal>NDB Cluster</literal> (Disk Data): Repeated
+          <literal>CREATE</literal> - <literal>INSERT</literal> -
+          <literal>DROP</literal> operations on Disk Data tables could
+          cause the MySQL table definition cache to become corrupt, so
+          that some <command>mysqld</command> processes could access
+          table information but others could not. (Bug #18595)
         </para>
       </listitem>
 
       <listitem>
         <para>
+          The <filename>fill_help_tables.sql</filename> file did not
+          load properly if the <literal>ANSI_QUOTES</literal> SQL mode
+          was enabled. (Bug #20542)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          The <filename>fill_help_tables.sql</filename> file did not
+          contain a <literal>SET NAMES 'utf8'</literal> statement to
+          indicate its encoding. This caused problems for some settings
+          of the MySQL character set such as <literal>big5</literal>.
+          (Bug #20551)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           The <option>--default-storage-engine</option> server option
           did not work. (Bug #20168)
         </para>

Thread
svn commit - mysqldoc@docsrva: r2446 - in trunk: . refman-commonpaul20 Jun