List:Commits« Previous MessageNext Message »
From:paul Date:January 6 2006 5:50am
Subject:svn commit - mysqldoc@docsrva: r704 - in trunk: . refman-common
View as plain text  
Author: paul
Date: 2006-01-06 06:50:20 +0100 (Fri, 06 Jan 2006)
New Revision: 704

Log:
 r5910@frost:  paul | 2006-01-05 23:50:05 -0600
 Documented bugfixes:
 Bug#10716
 Bug#14583
 Bug#14863
 Bug#15623
 Bug#15630
 Bug#15668
 Bug#15815


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:5905
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:1933
   + b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:5910
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:1933

Modified: trunk/refman-common/news-4.1.xml
===================================================================
--- trunk/refman-common/news-4.1.xml	2006-01-06 04:02:38 UTC (rev 703)
+++ trunk/refman-common/news-4.1.xml	2006-01-06 05:50:20 UTC (rev 704)
@@ -182,6 +182,14 @@
 
       <listitem>
         <para>
+          <literal>InnoDB</literal>: Comparison of indexed
+          <literal>VARCHAR CHARACTER SET ucs2 COLLATE ucs2_bin</literal>
+          columns using <literal>LIKE</literal> could fail. (Bug #14583)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           Issuing a <literal>DROP USER</literal> command could cause
           some users to encounter a
           <literal><replaceable>hostname</replaceable> is not allowed to
@@ -199,7 +207,7 @@
 
       <listitem>
         <para>
-          Symbolic links did not funciton properly on Windows platforms.
+          Symbolic links did not function properly on Windows platforms.
           (Bug #14960, Bug #14310)
         </para>
       </listitem>
@@ -402,6 +410,13 @@
 
       <listitem>
         <para>
+          <literal>PROCEDURE ANALYSE()</literal> could suggest a data
+          type with a negative display width. (Bug #10716)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           <literal>InnoDB</literal>: During replication, There was a
           failure to record events in the binary log that still occurred
           even in the event of a <literal>ROLLBACK</literal>. For

Modified: trunk/refman-common/news-5.0.xml
===================================================================
--- trunk/refman-common/news-5.0.xml	2006-01-06 04:02:38 UTC (rev 703)
+++ trunk/refman-common/news-5.0.xml	2006-01-06 05:50:20 UTC (rev 704)
@@ -207,6 +207,21 @@
 
       <listitem>
         <para>
+          <literal>InnoDB</literal>: Comparison of indexed
+          <literal>VARCHAR CHARACTER SET ucs2 COLLATE ucs2_bin</literal>
+          columns using <literal>LIKE</literal> could fail. (Bug #14583)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          An attempt to open a table that requires a disabled storage
+          engine could cause a server crash. (Bug #15185)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           Issuing a <literal>DROP USER</literal> command could cause
           some users to encounter a
           <literal><replaceable>hostname</replaceable> is not allowed to
@@ -293,6 +308,14 @@
 
       <listitem>
         <para>
+          Creating a trigger caused a server crash if the table or
+          trigger database was not known because no default database had
+          been selected. (Bug #14863)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           <literal>SHOW [FULL] COLUMNS</literal> and <literal>SHOW INDEX
           FROM</literal> did not function with temporary tables. (Bug
           #14271, Bug #14387, Bug #15224)
@@ -562,7 +585,22 @@
 
       <listitem>
         <para>
-          Symbolic links did not funciton properly on Windows platforms.
+          Corrected an error-handling problem within stored routines on
+          64-bit platforms. (Bug #15630)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Slave SQL thread cleanup was not handled properly on Mac OS X
+          when a statement was killed, resulting in a slave crash. (Bug
+          #15623, Bug #15668)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Symbolic links did not function properly on Windows platforms.
           (Bug #14960, Bug #14310)
         </para>
       </listitem>

Modified: trunk/refman-common/news-5.1.xml
===================================================================
--- trunk/refman-common/news-5.1.xml	2006-01-06 04:02:38 UTC (rev 703)
+++ trunk/refman-common/news-5.1.xml	2006-01-06 05:50:20 UTC (rev 704)
@@ -95,6 +95,22 @@
 
       <listitem>
         <para>
+          <literal>InnoDB</literal>: Comparison of indexed
+          <literal>VARCHAR CHARACTER SET ucs2 COLLATE ucs2_bin</literal>
+          columns using <literal>LIKE</literal> could fail. (Bug #14583)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Creating a trigger caused a server crash if the table or
+          trigger database was not known because no default database had
+          been selected. (Bug #14863)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           Issuing a <literal>DROP USER</literal> command could cause
           some users to encounter a
           <literal><replaceable>hostname</replaceable> is not allowed to

Thread
svn commit - mysqldoc@docsrva: r704 - in trunk: . refman-commonpaul6 Jan