Author: paul
Date: 2007-07-27 07:32:16 +0200 (Fri, 27 Jul 2007)
New Revision: 7248
Log:
r23089@frost: paul | 2007-07-27 00:29:08 -0500
Document bugfixes:
Bug#22427
Bug#24192
Bug#29310
Bug#29360
Bug#29431
Bug#29499
Bug#29604
Bug#29739
Bug#29740
Bug#29788
Bug#29850
Bug#29911
Modified:
trunk/refman-4.1/news-4.1.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:27992
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:23051
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:27992
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:23089
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:18941
Modified: trunk/refman-4.1/news-4.1.xml
===================================================================
--- trunk/refman-4.1/news-4.1.xml 2007-07-26 22:54:48 UTC (rev 7247)
+++ trunk/refman-4.1/news-4.1.xml 2007-07-27 05:32:16 UTC (rev 7248)
Changed blocks: 2, Lines Added: 8, Lines Deleted: 1; 983 bytes
@@ -201,6 +201,13 @@
<listitem>
<para>
+ Adding <literal>DISTINCT</literal> could cause incorrect rows
+ to appear in a query result. (Bug #29911)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<literal>SELECT ... INTO OUTFILE</literal> followed by
<literal>LOAD DATA</literal> could result in garbled
characters when the <literal>FIELDS ENCLOSED BY</literal>
@@ -3040,7 +3047,7 @@
<literal>NDB Cluster</literal>: Some queries having a
<literal>WHERE</literal> clause of the form <literal>c1=val1
OR c2 LIKE 'val2'</literal> were not evaluated correctly. (Bug
- # 17421)
+ #17421)
</para>
</listitem>
Modified: trunk/refman-5.0/releasenotes-es-5.0.xml
===================================================================
--- trunk/refman-5.0/releasenotes-es-5.0.xml 2007-07-26 22:54:48 UTC (rev 7247)
+++ trunk/refman-5.0/releasenotes-es-5.0.xml 2007-07-27 05:32:16 UTC (rev 7248)
Changed blocks: 2, Lines Added: 102, Lines Deleted: 8; 4150 bytes
@@ -80,14 +80,6 @@
</remark>
<itemizedlist>
-
- <listitem>
- <para>
- An incorrect result was returned when comparing string values
- <literal>CAST</literal> to time values.
- (Bug# 29555)
- </para>
- </listitem>
<listitem>
<para>
@@ -101,6 +93,108 @@
<listitem>
<para>
+ <command>mysqldump</command> produced output that incorrectly
+ discarded the <literal>NO_AUTO_VALUE_ON_ZERO</literal> value
+ of the <literal>SQL_MODE</literal> variable after dumping
+ triggers. (Bug #29788)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A statement of the form <literal>CREATE TABLE IF NOT EXISTS t1
+ SELECT f1() AS i</literal> failed with a deadlock error if the
+ stored function <literal>f1()</literal> referred to a table
+ with the same name as the to-be-created table. Now it
+ correctly produces a message that the table already exists.
+ (Bug #22427)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Adding <literal>DISTINCT</literal> could cause incorrect rows
+ to appear in a query result. (Bug #29911)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Killing an <literal>INSERT DELAYED</literal> thread caused a
+ server crash. (Bug #29431)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The special <quote>zero</quote> <literal>ENUM</literal> value
+ was coerced to the normal empty string <literal>ENUM</literal>
+ value during a column-to-column copy. This affected
+ <literal>CREATE ... SELECT</literal> statements and
+ <literal>SELECT</literal> statements with aggregate functions
+ on <literal>ENUM</literal> columns in the <literal>GROUP
+ BY</literal> clause. (Bug #29360)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Conversion of ASCII DEL (<literal>0x7F</literal>) to Unicode
+ incorrectly resulted in QUESTION MARK
+ (<literal>0x3F</literal>) rather than DEL. (Bug #29499)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A left join between two views could produce incorrect results.
+ (Bug #29604)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ For <literal>MEMORY</literal> tables, the
+ <literal>index_merge</literal> union access method could
+ return incorrect results. (Bug #29740)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ If query execution involved a temporary table,
+ <literal>GROUP_CONCAT()</literal> could return a result with
+ an incorrect character set. (Bug #29850)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Slave servers could incorrectly interpret an out-of-memory
+ error from the master and reconnect using the wrong binary log
+ position. (Bug #24192)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Comparison of <literal>TIME</literal> values using the
+ <literal>BETWEEN</literal> operator led to string comparison,
+ producing incorrect results in some cases. Now the values are
+ compared as integers. (Bug #29739)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ An incorrect result was returned when comparing string values
+ that were converted to <literal>TIME</literal> values with
+ <literal>CAST()</literal>. (Bug #29555)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
On Windows, the <command>mysql</command> client died if the
user entered a statement and Return after entering Control-C.
(Bug #29469)
Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml 2007-07-26 22:54:48 UTC (rev 7247)
+++ trunk/refman-5.1/news-5.1.xml 2007-07-27 05:32:16 UTC (rev 7248)
Changed blocks: 4, Lines Added: 113, Lines Deleted: 10; 5115 bytes
@@ -80,14 +80,6 @@
</remark>
<itemizedlist>
-
- <listitem>
- <para>
- An incorrect result was returned when comparing string values
- <literal>CAST</literal> to time values.
- (Bug# 29555)
- </para>
- </listitem>
<listitem>
<para>
@@ -185,6 +177,117 @@
<listitem>
<para>
+ <command>mysqldump</command> produced output that incorrectly
+ discarded the <literal>NO_AUTO_VALUE_ON_ZERO</literal> value
+ of the <literal>SQL_MODE</literal> variable after dumping
+ triggers. (Bug #29788)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A statement of the form <literal>CREATE TABLE IF NOT EXISTS t1
+ SELECT f1() AS i</literal> failed with a deadlock error if the
+ stored function <literal>f1()</literal> referred to a table
+ with the same name as the to-be-created table. Now it
+ correctly produces a message that the table already exists.
+ (Bug #22427)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Adding <literal>DISTINCT</literal> could cause incorrect rows
+ to appear in a query result. (Bug #29911)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Killing an <literal>INSERT DELAYED</literal> thread caused a
+ server crash. (Bug #29431)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ For updates to <literal>InnoDB</literal> tables, a
+ <literal>TIMESTAMP</literal> column with the <literal>ON
+ UPDATE CURRENT_TIMESTAMP</literal> attribute could be updated
+ even when no values actually changed. (Bug #29310)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The special <quote>zero</quote> <literal>ENUM</literal> value
+ was coerced to the normal empty string <literal>ENUM</literal>
+ value during a column-to-column copy. This affected
+ <literal>CREATE ... SELECT</literal> statements and
+ <literal>SELECT</literal> statements with aggregate functions
+ on <literal>ENUM</literal> columns in the <literal>GROUP
+ BY</literal> clause. (Bug #29360)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Conversion of ASCII DEL (<literal>0x7F</literal>) to Unicode
+ incorrectly resulted in QUESTION MARK
+ (<literal>0x3F</literal>) rather than DEL. (Bug #29499)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A left join between two views could produce incorrect results.
+ (Bug #29604)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ For <literal>MEMORY</literal> tables, the
+ <literal>index_merge</literal> union access method could
+ return incorrect results. (Bug #29740)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ If query execution involved a temporary table,
+ <literal>GROUP_CONCAT()</literal> could return a result with
+ an incorrect character set. (Bug #29850)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Slave servers could incorrectly interpret an out-of-memory
+ error from the master and reconnect using the wrong binary log
+ position. (Bug #24192)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Comparison of <literal>TIME</literal> values using the
+ <literal>BETWEEN</literal> operator led to string comparison,
+ producing incorrect results in some cases. Now the values are
+ compared as integers. (Bug #29739)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ An incorrect result was returned when comparing string values
+ that were converted to <literal>TIME</literal> values with
+ <literal>CAST()</literal>. (Bug #29555)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
If <literal>InnoDB</literal> reached its limit on the number
of concurrent transactions (1023), it wrote a descriptive
message to the error log but returned a misleading error
@@ -21149,7 +21252,7 @@
<literal>NDB Cluster</literal>: Some queries having a
<literal>WHERE</literal> clause of the form <literal>c1=val1
OR c2 LIKE 'val2'</literal> were not evaluated correctly. (Bug
- # 17421)
+ #17421)
</para>
</listitem>
@@ -23088,7 +23191,7 @@
<para>
<literal>NDB Cluster</literal>: In asynchronous replication
scenarios, binary log events could be lost on the remote
- <command>mysqld</command>. (Bug # 18472)
+ <command>mysqld</command>. (Bug #18472)
</para>
</listitem>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r7248 - in trunk: . refman-4.1 refman-5.0 refman-5.1 | paul | 27 Jul |
