List:Commits« Previous MessageNext Message »
From:paul Date:September 13 2006 5:59pm
Subject:svn commit - mysqldoc@docsrva: r3344 - in trunk: . refman-4.1 refman-5.0 refman-5.1
View as plain text  
Author: paul
Date: 2006-09-13 19:59:44 +0200 (Wed, 13 Sep 2006)
New Revision: 3344

Log:
 r13711@polar:  paul | 2006-09-13 13:01:23 -0500
 Document bugfixes:
 Bug#19243
 Bug#21054
 Bug#21113
 Bug#21676
 Bug#21774
 Bug#21813


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

Property changes on: trunk
___________________________________________________________________
Name: svk:merge
   - 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:13709
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:10300
   + 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:13711
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:10300


Modified: trunk/refman-4.1/news-4.1.xml
===================================================================
--- trunk/refman-4.1/news-4.1.xml	2006-09-13 17:21:17 UTC (rev 3343)
+++ trunk/refman-4.1/news-4.1.xml	2006-09-13 17:59:44 UTC (rev 3344)
Changed blocks: 3, Lines Added: 16, Lines Deleted: 8; 1691 bytes

@@ -200,14 +200,6 @@
 
       <listitem>
         <para>
-          <literal>NDB Cluster</literal>: <command>ndb_size.pl</command>
-          and <command>ndb_error_reporter</command> were missing from
-          RPM packages. (Bug #20426)
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
           The <command>ndb_mgm</command> program was included in both
           the <literal>MySQL-ndb-tools</literal> and
           <literal>MySQL-ndb-management</literal> RPM packages,

@@ -219,6 +211,14 @@
 
       <listitem>
         <para>
+          The <literal>myisam_stats_method</literal> variable was
+          mishandled when set from an option file or on the command
+          line. (Bug #21054)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           <literal>libmysqld</literal> produced some warnings to
           <literal>stderr</literal> which could not be silenced. These
           warnings now are suppressed. (Bug #13717)

@@ -379,6 +379,14 @@
 
       <listitem>
         <para>
+          <literal>NDB Cluster</literal>: <command>ndb_size.pl</command>
+          and <command>ndb_error_reporter</command> were missing from
+          RPM packages. (Bug #20426)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           <literal>NDB Cluster</literal>: Setting
           <literal>TransactionDeadlockDetectionTimeout</literal> to a
           value greater than 12000 would cause scans to deadlock, time


Modified: trunk/refman-5.0/news-5.0.xml
===================================================================
--- trunk/refman-5.0/news-5.0.xml	2006-09-13 17:21:17 UTC (rev 3343)
+++ trunk/refman-5.0/news-5.0.xml	2006-09-13 17:59:44 UTC (rev 3344)
Changed blocks: 1, Lines Added: 14, Lines Deleted: 0; 817 bytes

@@ -378,6 +378,20 @@
 
       <listitem>
         <para>
+          <literal>INNODB</literal> was slow with more than 100,000
+          <filename>.idb</filename> files. (Bug #21112)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>SHOW INNODB STATUS</literal> contained some duplicate
+          output. (Bug #21113)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           Using cursors with <literal>READ COMMITTED</literal> isolation
           level could cause <literal>InnoDB</literal> to crash. (Bug
           #19834)


Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml	2006-09-13 17:21:17 UTC (rev 3343)
+++ trunk/refman-5.1/news-5.1.xml	2006-09-13 17:59:44 UTC (rev 3344)
Changed blocks: 4, Lines Added: 54, Lines Deleted: 0; 2758 bytes

@@ -671,6 +671,36 @@
 
       <listitem>
         <para>
+          <literal>INNODB</literal> was slow with more than 100,000
+          <filename>.idb</filename> files. (Bug #21112)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>SHOW INNODB STATUS</literal> contained some duplicate
+          output. (Bug #21113)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          After an <literal>INSERT ... ON DUPLICATE KEY UPDATE</literal>
+          statement that updated an existing row,
+          <literal>LAST_INSERT_ID()</literal> could return a value not
+          in the table. (Bug #11460)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Selecting from <literal>INFORMATION_SCHEMA.FILES</literal>
+          could crash the server. (Bug #21676)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           Using cursors with <literal>READ COMMITTED</literal> isolation
           level could cause <literal>InnoDB</literal> to crash. (Bug
           #19834)

@@ -752,6 +782,14 @@
 
       <listitem>
         <para>
+          The <literal>myisam_stats_method</literal> variable was
+          mishandled when set from an option file or on the command
+          line. (Bug #21054)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           The optimizer assumed that if <literal>(a=x AND b=x)</literal>
           is true, <literal>(a=x AND b=x) AND a=b</literal> is also
           true. But that is not always so if <literal>a</literal> and

@@ -789,6 +827,14 @@
 
       <listitem>
         <para>
+          <literal>INSERT ... SELECT</literal> sometimes generated a
+          spurious <literal>Column count doesn't match value
+          count</literal> error. (Bug #21774)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           to the client could have an empty column name. When using
           tables created under MySQL 4.1 with a 5.0 server, if the
           tables contained <literal>VARCHAR</literal> columns, for some

@@ -1025,6 +1071,14 @@
 
       <listitem>
         <para>
+          A <literal>NUL</literal> byte within a prepared statement
+          string caused the rest of the string not to be written to the
+          query log, allowing logging to be bypassed. (Bug #21813)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           <command>mysql_upgrade</command> created temporary files in a
           possibly insecure way. (Bug #21224)
         </para>


Thread
svn commit - mysqldoc@docsrva: r3344 - in trunk: . refman-4.1 refman-5.0 refman-5.1paul13 Sep