List:Commits« Previous MessageNext Message »
From:paul Date:April 14 2006 2:48pm
Subject:svn commit - mysqldoc@docsrva: r1823 - in trunk: . refman-common
View as plain text  
Author: paul
Date: 2006-04-14 16:48:10 +0200 (Fri, 14 Apr 2006)
New Revision: 1823

Log:
 r9452@frost:  paul | 2006-04-14 09:47:45 -0500
 Document bugfixes:
 Bug#13158
 Bug#13571
 Bug#13601
 Bug#13683
 Bug#15917
 Bug#16504
 Bug#19021


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:6636
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:9446
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:4334
   + 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:6636
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:9452
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:4334

Modified: trunk/refman-common/news-4.1.xml
===================================================================
--- trunk/refman-common/news-4.1.xml	2006-04-14 13:56:18 UTC (rev 1822)
+++ trunk/refman-common/news-4.1.xml	2006-04-14 14:48:10 UTC (rev 1823)
@@ -183,6 +183,13 @@
         </para>
       </listitem>
 
+      <listitem>
+        <para>
+          Large file support was re-enabled for the MySQL server binary
+          for the AIX 5.2 platform. (Bug #13571)
+        </para>
+      </listitem>
+
     </itemizedlist>
 
     <para>
@@ -219,6 +226,13 @@
 
       <listitem>
         <para>
+          <command>mysql_config</command> returned incorrect libraries
+          on <literal>x86_64</literal> systems. (Bug #13158)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           <literal>mysql_reconnect()</literal> sent a <literal>SET
           NAMES</literal> statement to the server, even for pre-4.1
           servers that do not understand the statement. (Bug #18830)

Modified: trunk/refman-common/news-5.0.xml
===================================================================
--- trunk/refman-common/news-5.0.xml	2006-04-14 13:56:18 UTC (rev 1822)
+++ trunk/refman-common/news-5.0.xml	2006-04-14 14:48:10 UTC (rev 1823)
@@ -207,6 +207,17 @@
         </para>
       </listitem>
 
+      <listitem>
+        <para>
+          In result set metadata, the
+          <literal>MYSQL_FIELD.length</literal> value for
+          <literal>BIT</literal> columns now is reported in number of
+          bits. For example, the value for a <literal>BIT(9)</literal>
+          column is 9. (Formerly, the value was related to number of
+          bytes.) (Bug #13601)
+        </para>
+      </listitem>
+
     </itemizedlist>
 
     <para>
@@ -260,6 +271,40 @@
 
       <listitem>
         <para>
+          <literal>INSERT DELAYED</literal> into a view caused an
+          infinite loop. (Bug #13683)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Lettercase in database name qualifiers was not consistently
+          handled properly in queries when
+          <literal>lower_case_table_names</literal> was set to 1. (Bug
+          #15917)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          The optimizer could cause a server crash or use a non-optimal
+          subset of indexes when evaluating whether to use
+          <literal>Index Merge/Intersection</literal> variant of
+          <literal>index_merge</literal> optimization. (Bug #19021)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          The presence of multiple equalities in a condition after
+          reading a constant table could cause the optimizer not to use
+          an index. This resulted in certain queries being much slower
+          than in MySQL 4.1. (Bug #16504)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           A recent change caused the <command>mysql</command> client not
           to display <literal>NULL</literal> values correctly and to
           display numeric columns left-justified rather than
@@ -504,6 +549,13 @@
         </para>
       </listitem>
 
+      <listitem>
+        <para>
+          Large file support was re-enabled for the MySQL server binary
+          for the AIX 5.2 platform. (Bug #13571)
+        </para>
+      </listitem>
+
     </itemizedlist>
 
     <para>
@@ -514,6 +566,13 @@
 
       <listitem>
         <para>
+          <command>mysql_config</command> returned incorrect libraries
+          on <literal>x86_64</literal> systems. (Bug #13158)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           Stored routine names longer than 64 characters were silently
           truncated. Now the limit is properly enforced and an error
           occurs. (Bug #17015)

Modified: trunk/refman-common/news-5.1.xml
===================================================================
--- trunk/refman-common/news-5.1.xml	2006-04-14 13:56:18 UTC (rev 1822)
+++ trunk/refman-common/news-5.1.xml	2006-04-14 14:48:10 UTC (rev 1823)
@@ -68,13 +68,13 @@
       Uncomment following when there are new features or feature changes
       to report.
     </remark>
-    
+
     <para>
       Functionality added or changed:
     </para>
-    
+
     <itemizedlist>
-      
+
       <listitem>
         <para>
           <literal>NDB Cluster</literal>: It is now possible to perform
@@ -83,7 +83,18 @@
           all configured data nodes first. (Bug #18606)
         </para>
       </listitem>
-      
+
+      <listitem>
+        <para>
+          In result set metadata, the
+          <literal>MYSQL_FIELD.length</literal> value for
+          <literal>BIT</literal> columns now is reported in number of
+          bits. For example, the value for a <literal>BIT(9)</literal>
+          column is 9. (Formerly, the value was related to number of
+          bytes.) (Bug #13601)
+        </para>
+      </listitem>
+
     </itemizedlist>
 
     <para>
@@ -91,24 +102,24 @@
     </para>
 
     <itemizedlist>
-      
+
       <listitem>
         <para>
           The <literal>ExtractValue()</literal> function failed with a
           syntax error when the XPath expression used special characters
           such as <literal>&Ntilde;</literal> (<quote>N-tilde</quote>).
-          (Bug #16233)  
+          (Bug #16233)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           Inserts failed with duplicate key errors on a table
-          partitioned using an <literal>AUTO_INCREMENT</literal>
-          column for the partitioning key. (Bug #18552, Bug #18753) 
+          partitioned using an <literal>AUTO_INCREMENT</literal> column
+          for the partitioning key. (Bug #18552, Bug #18753)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           Delimited identifiers for partitions were not being treated
@@ -117,7 +128,7 @@
           characters. (Bug #18750)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           A query on a table partitioned or subpartitioned by
@@ -126,7 +137,7 @@
           in the hashing expression. (Bug #18423, Bug #18329)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           If the server were built without partition support, it was
@@ -137,7 +148,7 @@
           <option>&ddash;with-partition</option> option. (Bug #15561)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           <literal>NDB Cluster</literal>: In a 2-node cluster with a
@@ -146,14 +157,13 @@
           to come up partitioned (<quote>split-brain</quote> issue).
           (Bug #16447)
         </para>
-        
+
         <para>
-          A similar issue could occur when the cluster was first
-          started with a sufficiently low value for this parameter. (Bug
-          #18612)
+          A similar issue could occur when the cluster was first started
+          with a sufficiently low value for this parameter. (Bug #18612)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           <literal>NDB Cluster</literal>: On systems with multiple
@@ -164,7 +174,7 @@
           temporary outage. (Bug #15695)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           <literal>NDB Cluster</literal>: Unused open handlers for
@@ -173,7 +183,7 @@
           following an <literal>ALTER TABLE</literal>. (Bug #13228)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           <literal>NDB Cluster</literal>: Uninitialised internal
@@ -184,10 +194,20 @@
 
       <listitem>
         <para>
+          The presence of multiple equalities in a condition after
+          reading a constant table could cause the optimizer not to use
+          an index. This resulted in certain queries being much slower
+          than in MySQL 4.1. (Bug #16504)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           A recent change caused the <command>mysql</command> client not
           to display <literal>NULL</literal> values correctly and to
           display numeric columns left-justified rather than
-          right-justified. The problems have been corrected. (Bug #18265)
+          right-justified. The problems have been corrected. (Bug
+          #18265)
         </para>
       </listitem>
 
@@ -319,6 +339,13 @@
         </para>
       </listitem>
 
+      <listitem>
+        <para>
+          Large file support was re-enabled for the MySQL server binary
+          for the AIX 5.2 platform. (Bug #13571)
+        </para>
+      </listitem>
+
     </itemizedlist>
 
     <para>
@@ -329,6 +356,13 @@
 
       <listitem>
         <para>
+          <command>mysql_config</command> returned incorrect libraries
+          on <literal>x86_64</literal> systems. (Bug #13158)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           <literal>mysql_reconnect()</literal> sent a <literal>SET
           NAMES</literal> statement to the server, even for pre-4.1
           servers that do not understand the statement. (Bug #18830)

Thread
svn commit - mysqldoc@docsrva: r1823 - in trunk: . refman-commonpaul14 Apr