Author: paul
Date: 2006-09-25 22:15:50 +0200 (Mon, 25 Sep 2006)
New Revision: 3455
Log:
r14030@polar: paul | 2006-09-25 15:18:37 -0500
Document bugfixes:
Bug#16081
Bug#19419
Bug#20256
Bug#20863
Bug#21302
Bug#21392
Bug#21531
Modified:
trunk/refman-4.1/news-4.1.xml
trunk/refman-4.1/sql-syntax.xml
trunk/refman-5.0/news-5.0.xml
trunk/refman-5.0/sql-syntax.xml
trunk/refman-5.1/news-5.1.xml
trunk/refman-5.1/sql-syntax.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:14027
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:8616
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:10466
+ 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:14030
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:8616
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:10466
Modified: trunk/refman-4.1/news-4.1.xml
===================================================================
--- trunk/refman-4.1/news-4.1.xml 2006-09-25 19:24:49 UTC (rev 3454)
+++ trunk/refman-4.1/news-4.1.xml 2006-09-25 20:15:50 UTC (rev 3455)
Changed blocks: 1, Lines Added: 14, Lines Deleted: 0; 862 bytes
@@ -209,6 +209,20 @@
<listitem>
<para>
+ Table aliases in multiple-table <literal>DELETE</literal>
+ statements sometimes were not resolved. (Bug #21392)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>EXPORT_SET()</literal> did not accept arguments with
+ coercible character sets. (Bug #21531)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
The <option>--collation-server</option> server option was
being ignored. With the fix for this problem, if you choose a
non-default character set with
Modified: trunk/refman-4.1/sql-syntax.xml
===================================================================
--- trunk/refman-4.1/sql-syntax.xml 2006-09-25 19:24:49 UTC (rev 3454)
+++ trunk/refman-4.1/sql-syntax.xml 2006-09-25 20:15:50 UTC (rev 3455)
Changed blocks: 1, Lines Added: 2, Lines Deleted: 2; 695 bytes
@@ -8272,8 +8272,8 @@
<firstterm>row constructors</firstterm>. The two are
equivalent. They are legal in other contexts as well. For
example, the following two statements are semantically
- equivalent (although currently only the second one can be
- optimized):
+ equivalent (although in MySQL ¤t-series; only the second
+ one can be optimized):
</para>
<programlisting>
Modified: trunk/refman-5.0/news-5.0.xml
===================================================================
--- trunk/refman-5.0/news-5.0.xml 2006-09-25 19:24:49 UTC (rev 3454)
+++ trunk/refman-5.0/news-5.0.xml 2006-09-25 20:15:50 UTC (rev 3455)
Changed blocks: 2, Lines Added: 47, Lines Deleted: 0; 2180 bytes
@@ -224,6 +224,38 @@
<listitem>
<para>
+ Row equalities (such as <literal>WHERE (a,b) = (c,d)</literal>
+ were not taken into account by the optimizer, resulting in
+ slow query execution. Now they are treated as conjunctions of
+ equalities between row elements. (Bug #16081)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Column names supplied for a view created on a master server
+ could be lost on a slave server. (Bug #19419)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ For a <literal>MyISAM</literal> table locked with
+ <literal>LOCK TABLES ...WRITE</literal>, queries optimized
+ using the <literal>index_merge</literal> method did not show
+ rows inserted with the lock in place. (Bug #20256)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Table aliases in multiple-table <literal>DELETE</literal>
+ statements sometimes were not resolved. (Bug #21392)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
A function result in a comparison was replaced with a constant
by the optimizer under some circumstances when this
optimization was invalid. (Bug #21698)
@@ -541,6 +573,21 @@
<listitem>
<para>
+ A query result could be sorted improperly when using
+ <literal>ORDER BY</literal> for the second table in a join.
+ (Bug #21302)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>EXPORT_SET()</literal> did not accept arguments with
+ coercible character sets. (Bug #21531)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
The <option>--collation-server</option> server option was
being ignored. With the fix for this problem, if you choose a
non-default character set with
Modified: trunk/refman-5.0/sql-syntax.xml
===================================================================
--- trunk/refman-5.0/sql-syntax.xml 2006-09-25 19:24:49 UTC (rev 3454)
+++ trunk/refman-5.0/sql-syntax.xml 2006-09-25 20:15:50 UTC (rev 3455)
Changed blocks: 1, Lines Added: 2, Lines Deleted: 2; 685 bytes
@@ -8924,8 +8924,8 @@
<firstterm>row constructors</firstterm>. The two are
equivalent. They are legal in other contexts as well. For
example, the following two statements are semantically
- equivalent (although currently only the second one can be
- optimized):
+ equivalent (although the first one cannot be optimized until
+ MySQL 5.0.26):
</para>
<programlisting>
Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml 2006-09-25 19:24:49 UTC (rev 3454)
+++ trunk/refman-5.1/news-5.1.xml 2006-09-25 20:15:50 UTC (rev 3455)
Changed blocks: 1, Lines Added: 48, Lines Deleted: 0; 2023 bytes
@@ -714,6 +714,54 @@
<listitem>
<para>
+ Row equalities (such as <literal>WHERE (a,b) = (c,d)</literal>
+ were not taken into account by the optimizer, resulting in
+ slow query execution. Now they are treated as conjunctions of
+ equalities between row elements. (Bug #16081)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ If the binary logging format was changed between the times
+ when a locked table was modified and when it was unlocked, the
+ binary log contents were incorrect. (Bug #20863)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Column names supplied for a view created on a master server
+ could be lost on a slave server. (Bug #19419)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ For a <literal>MyISAM</literal> table locked with
+ <literal>LOCK TABLES ...WRITE</literal>, queries optimized
+ using the <literal>index_merge</literal> method did not show
+ rows inserted with the lock in place. (Bug #20256)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Table aliases in multiple-table <literal>DELETE</literal>
+ statements sometimes were not resolved. (Bug #21392)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A query result could be sorted improperly when using
+ <literal>ORDER BY</literal> for the second table in a join.
+ (Bug #21302)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
The <option>--collation-server</option> server option was
being ignored. With the fix for this problem, if you choose a
non-default character set with
Modified: trunk/refman-5.1/sql-syntax.xml
===================================================================
--- trunk/refman-5.1/sql-syntax.xml 2006-09-25 19:24:49 UTC (rev 3454)
+++ trunk/refman-5.1/sql-syntax.xml 2006-09-25 20:15:50 UTC (rev 3455)
Changed blocks: 1, Lines Added: 2, Lines Deleted: 2; 687 bytes
@@ -10295,8 +10295,8 @@
<firstterm>row constructors</firstterm>. The two are
equivalent. They are legal in other contexts as well. For
example, the following two statements are semantically
- equivalent (although currently only the second one can be
- optimized):
+ equivalent (although the first one cannot be optimized until
+ MySQL 5.1.12):
</para>
<programlisting>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r3455 - in trunk: . refman-4.1 refman-5.0 refman-5.1 | paul | 25 Sep |
