Author: paul
Date: 2006-06-22 16:53:47 +0200 (Thu, 22 Jun 2006)
New Revision: 2473
Log:
r11595@frost: paul | 2006-06-22 09:51:04 -0500
Document bugfixes:
Bug#12982
Bug#13479
Bug#15558
Bug#17201
Bug#19407
Bug#20195
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:10808
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:11564
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:7663
+ 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:10808
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:11595
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-22 13:11:01 UTC (rev 2472)
+++ trunk/refman-common/news-4.1.xml 2006-06-22 14:53:47 UTC (rev 2473)
@@ -217,7 +217,7 @@
circumstances 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)
+ #18595)
</para>
</listitem>
@@ -338,6 +338,15 @@
<listitem>
<para>
+ The <literal>ARCHIVE</literal> storage engine does not support
+ <literal>TRUNCATE TABLE</literal>, but the server was not
+ returning an appropriate error when truncation of an
+ <literal>ARCHIVE</literal> table was attempted. (Bug #15558)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
An update that used a join of a table to itself and modified
the table on both sides of the join reported the table as
crashed. (Bug #18036)
Modified: trunk/refman-common/news-5.0.xml
===================================================================
--- trunk/refman-common/news-5.0.xml 2006-06-22 13:11:01 UTC (rev 2472)
+++ trunk/refman-common/news-5.0.xml 2006-06-22 14:53:47 UTC (rev 2473)
@@ -332,7 +332,7 @@
</para>
<itemizedlist>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: <literal>TEXT</literal>
@@ -397,7 +397,7 @@
circumstances 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)
+ #18595)
</para>
</listitem>
@@ -564,6 +564,53 @@
<listitem>
<para>
+ With settings of <literal>read_buffer_size</literal> >= 2G
+ and <literal>read_rnd_buffer_size</literal> >=2G,
+ <literal>LOAD DATA INFILE</literal> failed with no error
+ message or caused a server crash for files larger than 2GB.
+ (Bug #12982)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>REPLACE</literal> statements caused activation of
+ <literal>UPDATE</literal> triggers, not
+ <literal>DELETE</literal> and <literal>INSERT</literal>
+ triggers. (Bug #13479)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The thread for <literal>INSERT DELAYED</literal> rows was
+ maintaining a separate <literal>AUTO_INCREMENT</literal>
+ counter, resulting in incorrect values being assigned if
+ <literal>DELAYED</literal> and non-<literal>DELAYED</literal>
+ inserts were mixed. (Bug #20195)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <command>mysqldump</command> wrote an extra pair of
+ <literal>DROP DATABASE</literal> and <literal>CREATE
+ DATABASE</literal> statements if run with the
+ <option>--add-drop-database</option> option and the database
+ contained views. (Bug #17201)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ On 64-bit Windows systems, <literal>REGEXP</literal> for
+ regular expressions with exactly 31 characters did not work.
+ (Bug #19407)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
For <command>ndb_mgmd</command>, Valgrind revealed problems
that were corrected: A memory leak (Bug #19318); a dependency
on an uninitialized variable (Bug #20333).
Modified: trunk/refman-common/news-5.1.xml
===================================================================
--- trunk/refman-common/news-5.1.xml 2006-06-22 13:11:01 UTC (rev 2472)
+++ trunk/refman-common/news-5.1.xml 2006-06-22 14:53:47 UTC (rev 2473)
@@ -438,6 +438,45 @@
<listitem>
<para>
+ With settings of <literal>read_buffer_size</literal> >= 2G
+ and <literal>read_rnd_buffer_size</literal> >=2G,
+ <literal>LOAD DATA INFILE</literal> failed with no error
+ message or caused a server crash for files larger than 2GB.
+ (Bug #12982)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>REPLACE</literal> statements caused activation of
+ <literal>UPDATE</literal> triggers, not
+ <literal>DELETE</literal> and <literal>INSERT</literal>
+ triggers. (Bug #13479)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The thread for <literal>INSERT DELAYED</literal> rows was
+ maintaining a separate <literal>AUTO_INCREMENT</literal>
+ counter, resulting in incorrect values being assigned if
+ <literal>DELAYED</literal> and non-<literal>DELAYED</literal>
+ inserts were mixed. (Bug #20195)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <command>mysqldump</command> wrote an extra pair of
+ <literal>DROP DATABASE</literal> and <literal>CREATE
+ DATABASE</literal> statements if run with the
+ <option>--add-drop-database</option> option and the database
+ contained views. (Bug #17201)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Shutting down a slave in a replication scenario where
temporary tables are in use would cause the slave to produce a
core dump. (Bug #19881)
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r2473 - in trunk: . refman-common | paul | 22 Jun |
