Author: paul
Date: 2007-07-25 05:48:28 +0200 (Wed, 25 Jul 2007)
New Revision: 7201
Log:
r23014@frost: paul | 2007-07-24 22:45:46 -0500
Document bugfixes:
Bug#13326
Bug#21074
Bug#26141
Bug#28810
Bug#29469
Bug#29610
Modified:
trunk/falcon/news-falcon.xml
trunk/refman-5.0/releasenotes-es-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:27897
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:22908
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:18941
+ 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:27897
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:23014
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:18941
Modified: trunk/falcon/news-falcon.xml
===================================================================
--- trunk/falcon/news-falcon.xml 2007-07-25 03:13:46 UTC (rev 7200)
+++ trunk/falcon/news-falcon.xml 2007-07-25 03:48:28 UTC (rev 7201)
Changed blocks: 1, Lines Added: 9, Lines Deleted: 0; 807 bytes
@@ -59,6 +59,15 @@
<listitem>
<para>
+ For debug builds, the server crashed when inserting a negated
+ <literal>DECIMAL</literal> value of maximum precision (65
+ digits), such as for <literal>INSERT INTO ... SELECT -col_val
+ ...</literal> (Bug #28810)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Creating a tablespace with a unique name but using the same
datafile as an existing tablespace results in the
re-initialization of the tablespace and the loss of the data
Modified: trunk/refman-5.0/releasenotes-es-5.0.xml
===================================================================
--- trunk/refman-5.0/releasenotes-es-5.0.xml 2007-07-25 03:13:46 UTC (rev 7200)
+++ trunk/refman-5.0/releasenotes-es-5.0.xml 2007-07-25 03:48:28 UTC (rev 7201)
Changed blocks: 1, Lines Added: 53, Lines Deleted: 20; 4259 bytes
@@ -80,41 +80,74 @@
</remark>
<itemizedlist>
+
<listitem>
<para>
- Using the <literal>DATE()</literal> function in a
- <literal>WHERE</literal> clause did not return any records after
- encountering <literal>NULL</literal>.
- However, using <literal>TRIM</literal> or
- <literal>CAST</literal> produced the correct results.
- (Bug #29898)
+ <literal>NDB Cluster</literal>: The output from
+ <command>ndb_config</command>
+ <option>--config-file=<replaceable>file</replaceable></option>
+ was sent to <literal>stdout</literal> rather than
+ <literal>stderr</literal>. (Bug #25941)
</para>
</listitem>
-
+
<listitem>
<para>
- Using the <option>--skip-add-drop-table </option>option
- with <command>mysqldump</command> generated incorrect
- SQL if the database included any views. The recreation of views
- requires the creation and removal of temporary tables. This option
- suppressed the removal of those temporary tables. The same applied
- to <option>--compact</option> since this option also
- invokes <option>--skip-add-drop-table</option>. (Bug #28524)
+ On Windows, the <command>mysql</command> client died if the
+ user entered a statement and Return after entering Control-C.
+ (Bug #29469)
</para>
</listitem>
-
+
<listitem>
<para>
- <literal>NDB Cluster</literal>: The output from
- <command>ndb_config</command>
- <option>--config-file=<replaceable>file</replaceable></option>
- was sent to <literal>stdout</literal> rather than
- <literal>stderr</literal>. (Bug #25941)
+ For the general query log, logging of prepared statements
+ executed via the C API differed from logging of prepared
+ statements performed with <literal>PREPARE</literal> and
+ <literal>EXECUTE</literal>. Logging for the latter was missing
+ the <literal>Prepare</literal> and <literal>Execute</literal>
+ lines. (Bug #13326)
</para>
</listitem>
<listitem>
<para>
+ If an operation had an <literal>InnoDB</literal> table, and
+ two triggers, <literal>AFTER UPDATE</literal> and
+ <literal>AFTER INSERT</literal>, competing for different
+ resources (such as two distinct <literal>MyISAM</literal>
+ tables), the triggers were unable to execute concurrently. In
+ addition, <literal>INSERT</literal> and
+ <literal>UPDATE</literal> statements for the
+ <literal>InnoDB</literal> table were unable to run
+ concurrently. (Bug #26141)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Using the <literal>DATE()</literal> function in a
+ <literal>WHERE</literal> clause did not return any records
+ after encountering <literal>NULL</literal>. However, using
+ <literal>TRIM</literal> or <literal>CAST</literal> produced
+ the correct results. (Bug #29898)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Using the <option>--skip-add-drop-table </option>option with
+ <command>mysqldump</command> generated incorrect SQL if the
+ database included any views. The recreation of views requires
+ the creation and removal of temporary tables. This option
+ suppressed the removal of those temporary tables. The same
+ applied to <option>--compact</option> since this option also
+ invokes <option>--skip-add-drop-table</option>. (Bug #28524)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
A race condition in the interaction between
<literal>MyISAM</literal> and the query cache code caused the
query cache not to invalidate itself for concurrently inserted
Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml 2007-07-25 03:13:46 UTC (rev 7200)
+++ trunk/refman-5.1/news-5.1.xml 2007-07-25 03:48:28 UTC (rev 7201)
Changed blocks: 2, Lines Added: 72, Lines Deleted: 22; 4464 bytes
@@ -83,28 +83,6 @@
<listitem>
<para>
- Using the <literal>DATE()</literal> function in a
- <literal>WHERE</literal> clause did not return any records
- after encountering <literal>NULL</literal>. However, using
- <literal>TRIM</literal> or <literal>CAST</literal> produced
- the correct results. (Bug #29898)
- </para>
- </listitem>
-
- <listitem>
- <para>
- Using the <option>--skip-add-drop-table </option>option with
- <command>mysqldump</command> generated incorrect SQL if the
- database included any views. The recreation of views requires
- the creation and removal of temporary tables. This option
- suppressed the removal of those temporary tables. The same
- applied to <option>--compact</option> since this option also
- invokes <option>--skip-add-drop-table</option>. (Bug #28524)
- </para>
- </listitem>
-
- <listitem>
- <para>
<literal>NDB Cluster</literal>: The output from
<command>ndb_config</command>
<option>--config-file=<replaceable>file</replaceable></option>
@@ -199,6 +177,78 @@
<listitem>
<para>
+ On Windows, the <command>mysql</command> client died if the
+ user entered a statement and Return after entering Control-C.
+ (Bug #29469)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ For the general query log, logging of prepared statements
+ executed via the C API differed from logging of prepared
+ statements performed with <literal>PREPARE</literal> and
+ <literal>EXECUTE</literal>. Logging for the latter was missing
+ the <literal>Prepare</literal> and <literal>Execute</literal>
+ lines. (Bug #13326)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Under heavy load with a large query cache, invalidating part
+ of the cache could cause the server to freeze (that is, to be
+ unable to service other operations until the invalidation was
+ complete). (Bug #21074)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ If an operation had an <literal>InnoDB</literal> table, and
+ two triggers, <literal>AFTER UPDATE</literal> and
+ <literal>AFTER INSERT</literal>, competing for different
+ resources (such as two distinct <literal>MyISAM</literal>
+ tables), the triggers were unable to execute concurrently. In
+ addition, <literal>INSERT</literal> and
+ <literal>UPDATE</literal> statements for the
+ <literal>InnoDB</literal> table were unable to run
+ concurrently. (Bug #26141)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ On 64-bit platforms, the filesort code (for queries with
+ <literal>GROUP BY</literal> or <literal>ORDER BY</literal>)
+ could crash due to an incorrect pointer size. (Bug #29610)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Using the <literal>DATE()</literal> function in a
+ <literal>WHERE</literal> clause did not return any records
+ after encountering <literal>NULL</literal>. However, using
+ <literal>TRIM</literal> or <literal>CAST</literal> produced
+ the correct results. (Bug #29898)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Using the <option>--skip-add-drop-table </option>option with
+ <command>mysqldump</command> generated incorrect SQL if the
+ database included any views. The recreation of views requires
+ the creation and removal of temporary tables. This option
+ suppressed the removal of those temporary tables. The same
+ applied to <option>--compact</option> since this option also
+ invokes <option>--skip-add-drop-table</option>. (Bug #28524)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
A race condition in the interaction between
<literal>MyISAM</literal> and the query cache code caused the
query cache not to invalidate itself for concurrently inserted
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r7201 - in trunk: . falcon refman-5.0 refman-5.1 | paul | 25 Jul |
