Author: paul
Date: 2006-11-13 21:09:13 +0100 (Mon, 13 Nov 2006)
New Revision: 3925
Log:
r15646@polar: paul | 2006-11-13 14:07:36 -0600
Document bugfixes:
20894
21726
23949
20028
20732
11655
20927
21354
22728
23379
23037
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:15596
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:12012
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:11757
+ 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:15646
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:12012
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:11757
Modified: trunk/refman-4.1/news-4.1.xml
===================================================================
--- trunk/refman-4.1/news-4.1.xml 2006-11-13 13:44:41 UTC (rev 3924)
+++ trunk/refman-4.1/news-4.1.xml 2006-11-13 20:09:13 UTC (rev 3925)
Changed blocks: 3, Lines Added: 62, Lines Deleted: 2; 3101 bytes
@@ -185,6 +185,43 @@
<listitem>
<para>
+ For not-yet-authenticated connections, the
+ <literal>Time</literal> column in <literal>SHOW
+ PROCESSLIST</literal> was a random value rather than
+ <literal>NULL</literal>. (Bug #23379)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The <literal>Handler_rollback</literal> status variable
+ sometimes was incremented when no rollback had taken place.
+ (Bug #22728)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Lack of validation for input and output
+ <literal>TIME</literal> values resulted in several problems:
+ <literal>SEC_TO_TIME()</literal> within subqueries incorrectly
+ clipped large values; <literal>SEC_TO_TIME()</literal> treated
+ <literal>BIGINT UNSIGNED</literal> values as signed; only
+ truncation warnings were produced when both truncation and
+ out-of-range <literal>TIME</literal> values occurred. (Bug
+ #11655, Bug #20927)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Range searches on columns with an index prefix could miss
+ records. (Bug #20732)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Transient errors in replication from master to slave may
trigger multiple <literal>Got fatal error 1236: 'binlog
truncated in the middle of event'</literal> errors on the
@@ -298,6 +335,15 @@
<listitem>
<para>
+ Within a prepared statement, <literal>SELECT (COUNT(*) =
+ 1)</literal> (or similar use of other aggregate functions) did
+ not return the correct result for statement re-execution. (Bug
+ #21354)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<literal>DELETE IGNORE</literal> could hang for foreign key
parent deletes. (Bug #18819)
</para>
@@ -305,9 +351,23 @@
<listitem>
<para>
- The value of <literal>LAST_INSERT_ID()</literal> was not
- always updated correctly within stored routines. (Bug #21726)
+ Redundant binary log <literal>LAST_INSERT_ID</literal> events
+ could be generated;
+ <literal>LAST_INSERT_ID(<replaceable>expr</replaceable>)</literal>
+ didn't return the value of <replaceable>expr</replaceable>;
+ <literal>LAST_INSERT_ID()</literal> could return the value
+ generated by the current statement if the call happens after
+ value generation, as in:
</para>
+
+<programlisting>
+CREATE TABLE t1 (i INT AUTO_INCREMENT PRIMARY KEY, j INT);
+INSERT INTO t1 VALUES (NULL, 0), (NULL, LAST_INSERT_ID());
+</programlisting>
+
+ <para>
+ (Bug #21726)
+ </para>
</listitem>
<listitem>
Modified: trunk/refman-5.0/releasenotes-es-5.0.xml
===================================================================
--- trunk/refman-5.0/releasenotes-es-5.0.xml 2006-11-13 13:44:41 UTC (rev 3924)
+++ trunk/refman-5.0/releasenotes-es-5.0.xml 2006-11-13 20:09:13 UTC (rev 3925)
Changed blocks: 1, Lines Added: 82, Lines Deleted: 0; 3175 bytes
@@ -394,6 +394,88 @@
<listitem>
<para>
+ The column default value in the output from <literal>SHOW
+ COLUMNS</literal> or <literal>SELECT FROM
+ INFORMATION_SCHEMA.COLUMNS</literal> was truncated to 64
+ characters. (Bug #23037)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ For not-yet-authenticated connections, the
+ <literal>Time</literal> column in <literal>SHOW
+ PROCESSLIST</literal> was a random value rather than
+ <literal>NULL</literal>. (Bug #23379)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The <literal>Host</literal> column in <literal>SHOW
+ PROCESSLIST</literal> output was blank when the server was
+ started with the <option>--skip-grant-tables</option> option.
+ (Bug #22728)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The <literal>Handler_rollback</literal> status variable
+ sometimes was incremented when no rollback had taken place.
+ (Bug #22728)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Within a prepared statement, <literal>SELECT (COUNT(*) =
+ 1)</literal> (or similar use of other aggregate functions) did
+ not return the correct result for statement re-execution. (Bug
+ #21354)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Lack of validation for input and output
+ <literal>TIME</literal> values resulted in several problems:
+ <literal>SEC_TO_TIME()</literal> within subqueries incorrectly
+ clipped large values; <literal>SEC_TO_TIME()</literal> treated
+ <literal>BIGINT UNSIGNED</literal> values as signed; only
+ truncation warnings were produced when both truncation and
+ out-of-range <literal>TIME</literal> values occurred. (Bug
+ #11655, Bug #20927)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Range searches on columns with an index prefix could miss
+ records. (Bug #20732)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ With <literal>SQL_MODE=TRADITIONAL</literal>, MySQL
+ incorrectly aborted on warnings within stored routines and
+ triggers. (Bug #20028)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ In <command>mysql</command>, invoking
+ <literal>connect</literal> or <literal>\r</literal> with very
+ long <replaceable>db_name</replaceable> or
+ <replaceable>host_name</replaceable> parameters caused buffer
+ overflow. (Bug #20894)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<command>mysqldump --xml</command> produced invalid XML for
<literal>BLOB</literal> data. (Bug #19745)
</para>
Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml 2006-11-13 13:44:41 UTC (rev 3924)
+++ trunk/refman-5.1/news-5.1.xml 2006-11-13 20:09:13 UTC (rev 3925)
Changed blocks: 5, Lines Added: 98, Lines Deleted: 8; 5197 bytes
@@ -81,6 +81,14 @@
<listitem>
<para>
+ Binary distributions of MySQL 5.1.12 were built without
+ support for partitioning. This has been corrected except for
+ NetWare. (Bug #23949)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
A change in the interfaces for the
<literal>INFORMATION_SCHEMA.FILES</literal> table have made
the table accessible to storage engines other than
@@ -117,6 +125,88 @@
<listitem>
<para>
+ The column default value in the output from <literal>SHOW
+ COLUMNS</literal> or <literal>SELECT FROM
+ INFORMATION_SCHEMA.COLUMNS</literal> was truncated to 64
+ characters. (Bug #23037)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ For not-yet-authenticated connections, the
+ <literal>Time</literal> column in <literal>SHOW
+ PROCESSLIST</literal> was a random value rather than
+ <literal>NULL</literal>. (Bug #23379)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The <literal>Host</literal> column in <literal>SHOW
+ PROCESSLIST</literal> output was blank when the server was
+ started with the <option>--skip-grant-tables</option> option.
+ (Bug #22728)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The <literal>Handler_rollback</literal> status variable
+ sometimes was incremented when no rollback had taken place.
+ (Bug #22728)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Within a prepared statement, <literal>SELECT (COUNT(*) =
+ 1)</literal> (or similar use of other aggregate functions) did
+ not return the correct result for statement re-execution. (Bug
+ #21354)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Lack of validation for input and output
+ <literal>TIME</literal> values resulted in several problems:
+ <literal>SEC_TO_TIME()</literal> within subqueries incorrectly
+ clipped large values; <literal>SEC_TO_TIME()</literal> treated
+ <literal>BIGINT UNSIGNED</literal> values as signed; only
+ truncation warnings were produced when both truncation and
+ out-of-range <literal>TIME</literal> values occurred. (Bug
+ #11655, Bug #20927)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Range searches on columns with an index prefix could miss
+ records. (Bug #20732)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ With <literal>SQL_MODE=TRADITIONAL</literal>, MySQL
+ incorrectly aborted on warnings within stored routines and
+ triggers. (Bug #20028)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ In <command>mysql</command>, invoking
+ <literal>connect</literal> or <literal>\r</literal> with very
+ long <replaceable>db_name</replaceable> or
+ <replaceable>host_name</replaceable> parameters caused buffer
+ overflow. (Bug #20894)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<command>mysqldump --xml</command> produced invalid XML for
<literal>BLOB</literal> data. (Bug #19745)
</para>
@@ -1413,13 +1503,13 @@
by an index. (Bug #22384)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>ALTER EVENT</literal> statements including only a
<literal>COMMENT</literal> clause failed with a syntax error
on two platforms: Linux for S/390, and OS X 10.4 for 64-bit
- PPC. (Bug #23423)
+ PPC. (Bug #23423)
</para>
</listitem>
@@ -2661,8 +2751,8 @@
<listitem>
<para>
<literal>NDB Cluster</literal> (Disk Data):
- <command>mysqldump</command> did not back up tablespace or
- log file group information for Disk Data tables correctly.
+ <command>mysqldump</command> did not back up tablespace or log
+ file group information for Disk Data tables correctly.
(Specifically, <literal>UNDO_BUFFER_SIZE</literal> and
<literal>INITIAL_SIZE</literal> values were misreported.)
Trying to restore from such a backup would produce error 1296
@@ -4761,10 +4851,10 @@
<listitem>
<para>
- <literal>NDB Cluster</literal> (Disk Data): A data file created
- on one tablespace could be dropped using <literal>ALTER
- TABLESPACE ... DROP DATAFILE</literal> on a different
- tablespace. (Bug #20053)
+ <literal>NDB Cluster</literal> (Disk Data): A data file
+ created on one tablespace could be dropped using
+ <literal>ALTER TABLESPACE ... DROP DATAFILE</literal> on a
+ different tablespace. (Bug #20053)
</para>
</listitem>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r3925 - in trunk: . refman-4.1 refman-5.0 refman-5.1 | paul | 13 Nov |
