Author: paul
Date: 2006-05-04 19:30:34 +0200 (Thu, 04 May 2006)
New Revision: 2027
Log:
r7267@polar: paul | 2006-05-04 12:19:37 -0500
Document bugfixes:
Bug#1989
Bug#7643
Bug#16461
Bug#17368
Bug#17737
Bug#18399
Bug#18495
Bug#18767
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:7259
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:10071
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:4886
+ 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:7267
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:10071
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:4886
Modified: trunk/refman-common/news-4.1.xml
===================================================================
--- trunk/refman-common/news-4.1.xml 2006-05-04 14:51:29 UTC (rev 2026)
+++ trunk/refman-common/news-4.1.xml 2006-05-04 17:30:34 UTC (rev 2027)
@@ -190,6 +190,15 @@
<listitem>
<para>
+ No error message was being issued for storage engines that do
+ not support <literal>ALTER TABLE</literal>. Now an
+ <literal>ER_NOT_SUPPORTED_YET</literal> error occurs. (Bug
+ #7643)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
The binary log would create an incorrect
<literal>DROP</literal> query when creating temporary tables
during replication. (Bug #17263)
@@ -340,6 +349,18 @@
<listitem>
<para>
+ For single-<literal>SELECT</literal> union constructs of the
+ form (SELECT ... ORDER BY
+ <replaceable>order_list1</replaceable> [LIMIT
+ <replaceable>n</replaceable>]) ORDER BY
+ <replaceable>order_list2</replaceable>, the <literal>ORDER
+ BY</literal> lists were concatenated and the
+ <literal>LIMIT</literal> clause was ignored. (Bug #18767)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
The <literal>IN</literal>-to-<literal>EXISTS</literal>
transformation was making a reference to a parse tree fragment
that was left out of the parse tree. This caused problems with
Modified: trunk/refman-common/news-5.0.xml
===================================================================
--- trunk/refman-common/news-5.0.xml 2006-05-04 14:51:29 UTC (rev 2026)
+++ trunk/refman-common/news-5.0.xml 2006-05-04 17:30:34 UTC (rev 2027)
@@ -203,6 +203,14 @@
</para>
</listitem>
+ <listitem>
+ <para>
+ The bundled yaSSL library was upgraded to version 1.3.0. This
+ improves handling of certain problems with SSL-related command
+ options. (Bug #17737)
+ </para>
+ </listitem>
+
</itemizedlist>
<para>
@@ -476,6 +484,33 @@
<listitem>
<para>
+ Within a trigger, <literal>CONNECTION_ID()</literal> did not
+ return the connection ID of the thread that caused the trigger
+ to be activated. (Bug #16461)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The yaSSL library returned a cipher list in a manner
+ incompatible with OpenSSL. (Bug #18399)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ For single-<literal>SELECT</literal> union constructs of the
+ form (SELECT ... ORDER BY
+ <replaceable>order_list1</replaceable> [LIMIT
+ <replaceable>n</replaceable>]) ORDER BY
+ <replaceable>order_list2</replaceable>, the <literal>ORDER
+ BY</literal> lists were concatenated and the
+ <literal>LIMIT</literal> clause was ignored. (Bug #18767)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<literal>CREATE VIEW</literal> statements would not be
replicated to the slave if the
<option>--replicate-wild-ignore-table</option> rule was
Modified: trunk/refman-common/news-5.1.xml
===================================================================
--- trunk/refman-common/news-5.1.xml 2006-05-04 14:51:29 UTC (rev 2026)
+++ trunk/refman-common/news-5.1.xml 2006-05-04 17:30:34 UTC (rev 2027)
@@ -94,6 +94,25 @@
<listitem>
<para>
+ The bundled yaSSL library was upgraded to version 1.3.0. This
+ improves handling of certain problems with SSL-related command
+ options. (Bug #17737)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ For the <command>mysql</command> client, typing Control-C
+ causes <command>mysql</command> to attempt to kill the current
+ statement. If this cannot be done, or Control-C is typed again
+ before the statement is killed, <command>mysql</command>
+ exits. Previously, Control-C caused <command>mysql</command>
+ to exit in all cases. (Bug #1989)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Creating a table in an InnoDB database with a column name that
matched the name of an internal InnoDB table (including
<literal>DB_ROW_ID</literal>, <literal>DB_TRX_ID</literal>,
@@ -226,15 +245,6 @@
<listitem>
<para>
- Event-creation statements enclosed in multi-line comments
- using <literal>/*!<replaceable>version_number</replaceable>
- ... */</literal> syntax were not parsed correctly. (Bug
- #18078)
- </para>
- </listitem>
-
- <listitem>
- <para>
<literal>NDB Cluster</literal> (Replication): When taking part
in Cluster replication of tables containing
<literal>BLOB</literal> columns, <command>mysqld</command>
@@ -322,6 +332,54 @@
<listitem>
<para>
+ Event-creation statements enclosed in multi-line comments
+ using <literal>/*!<replaceable>version_number</replaceable>
+ ... */</literal> syntax were not parsed correctly. (Bug
+ #18078)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Within a trigger, <literal>CONNECTION_ID()</literal> did not
+ return the connection ID of the thread that caused the trigger
+ to be activated. (Bug #16461)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <command>mysqltest</command> incorrectly interpreted some
+ <literal>ER_<replaceable>xxx</replaceable></literal> error
+ names given in the <literal>error</literal> command. (Bug
+ #18495)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ For single-<literal>SELECT</literal> union constructs of the
+ form (SELECT ... ORDER BY
+ <replaceable>order_list1</replaceable> [LIMIT
+ <replaceable>n</replaceable>]) ORDER BY
+ <replaceable>order_list2</replaceable>, the <literal>ORDER
+ BY</literal> lists were concatenated and the
+ <literal>LIMIT</literal> clause was ignored. (Bug #18767)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Logging to the <literal>mysql.general_log</literal> and
+ <literal>mysql.slow_log</literal> tables did not work for
+ Windows builds because the <literal>CSV</literal> storage
+ engine was unavailable. The <literal>CSV</literal> engine now
+ is enabled in Windows builds. (Bug #17368)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<literal>LOAD DATA FROM MASTER</literal> would fail when
trying to load the <literal>INFORMATION_SCHEMA</literal>
database from the master, because the
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r2027 - in trunk: . refman-common | paul | 4 May |
