Author: jstephens
Date: 2007-06-10 21:05:23 +0200 (Sun, 10 Jun 2007)
New Revision: 6748
Log:
Knocked out a few P1 bugfixes:
Bug #12826, Bug #26842, Bug #28361, Bug #28492, Bug #28521 (Events),
Bug #28598, Bug #28605, Bug #28631, Bug #28728
Noted 5.1.17->5.1.18 upgrade issue with scheduled events.
Reformat.
Modified:
trunk/refman-5.0/releasenotes-es-5.0.xml
trunk/refman-5.1/events.xml
trunk/refman-5.1/news-5.1.xml
Modified: trunk/refman-5.0/releasenotes-es-5.0.xml
===================================================================
--- trunk/refman-5.0/releasenotes-es-5.0.xml 2007-06-10 17:22:37 UTC (rev 6747)
+++ trunk/refman-5.0/releasenotes-es-5.0.xml 2007-06-10 19:05:23 UTC (rev 6748)
Changed blocks: 1, Lines Added: 56, Lines Deleted: 0; 2541 bytes
@@ -99,6 +99,62 @@
<listitem>
<para>
+ After an upgrade, the names of stored routines referenced by
+ views were no longer displayed by <literal>SHOW CREATE
+ VIEW</literal>. This was a regression introduced by the fix
+ for Bug #23191. (Bug #28605)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Killing from one connection a long-running <literal>EXPLAIN
+ QUERY</literal> started from another connection caused
+ <command>mysqld</command> to crash. (Bug #28598)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Subselects returning <literal>LONG</literal> values in MySQL
+ versions later than 5.0.24a returned
+ <literal>LONGLONG</literal> prior to this. The previous
+ behavior was restored. This issue was introduced by the fix
+ for Bug #19714. (Bug #28492)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A buffer overflow could occur when using
+ <literal>DECIMAL</literal> columns on Windows operating
+ systems. (Bug #28361)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Executing <literal>EXPLAIN EXTENDED</literal> on a query using
+ a derived table over a grouping subselect could lead to a
+ server crash. This occurred only when materialization of the
+ derived tables required creation of an auxiliary temporary
+ table, an example being when a grouping operation was carried
+ out with usage of a temporary table. (Bug #28728)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Binary logging of prepared statements could produce
+ syntacticly incorrect queries in the binary log, replacing
+ some parameters with variable names rather than variable
+ values. This could lead to incorrect results on replication
+ slaves. (Bug #12826, Bug #26842)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<literal>NDB Cluster</literal>: When an API node sent more
than 1024 signals in a single batch, <literal>NDB</literal>
would process only the first 1024 of these, and then hang.
Modified: trunk/refman-5.1/events.xml
===================================================================
--- trunk/refman-5.1/events.xml 2007-06-10 17:22:37 UTC (rev 6747)
+++ trunk/refman-5.1/events.xml 2007-06-10 19:05:23 UTC (rev 6748)
Changed blocks: 1, Lines Added: 11, Lines Deleted: 0; 883 bytes
@@ -2043,6 +2043,17 @@
references are disallowed. (See Bug #22830 for more information.)
</para>
+ <para>
+ When upgrading to MySQL 5.1.18 or later from a previous MySQL
+ version where scheduled events were in use, the upgrade utilities
+ <command>mysql_upgrade</command> and
+ <command>mysql_fix_privilege_tables</command> do not accomodate
+ changes in system tables relating to the Event Scheduler. As a
+ workaround, you can dump events before the upgrade, then restore
+ them from the dump afterwards. This issue was fixed in MySQL
+ 5.1.20 (see Bug #28521).
+ </para>
+
</section>
</chapter>
Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml 2007-06-10 17:22:37 UTC (rev 6747)
+++ trunk/refman-5.1/news-5.1.xml 2007-06-10 19:05:23 UTC (rev 6748)
Changed blocks: 3, Lines Added: 86, Lines Deleted: 0; 3995 bytes
@@ -148,6 +148,71 @@
<listitem>
<para>
+ Attempting to create an index on a <literal>BIT</literal>
+ column failed after modifying the column. (Bug #28631)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ After an upgrade, the names of stored routines referenced by
+ views were no longer displayed by <literal>SHOW CREATE
+ VIEW</literal>. This was a regression introduced by the fix
+ for Bug #23191. (Bug #28605)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Killing from one connection a long-running <literal>EXPLAIN
+ QUERY</literal> started from another connection caused
+ <command>mysqld</command> to crash. (Bug #28598)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ When upgrading from MySQL 5.1.17 to 5.1.18,
+ <command>mysql_upgrade</command> and
+ <command>mysql_fix_privilege_tables</command> did not upgrade
+ the system tables relating to the Event Scheduler correctly.
+ (Bug #28521)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Subselects returning <literal>LONG</literal> values in MySQL
+ versions later than 5.0.24a returned
+ <literal>LONGLONG</literal> prior to this. The previous
+ behavior was restored. This issue was introduced by the fix
+ for Bug #19714. (Bug #28492)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Executing <literal>EXPLAIN EXTENDED</literal> on a query using
+ a derived table over a grouping subselect could lead to a
+ server crash. This occurred only when materialization of the
+ derived tables required creation of an auxiliary temporary
+ table, an example being when a grouping operation was carried
+ out with usage of a temporary table. (Bug #28728)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Binary logging of prepared statements could produce
+ syntacticly incorrect queries in the binary log, replacing
+ some parameters with variable names rather than variable
+ values. This could lead to incorrect results on replication
+ slaves. (Bug #12826, Bug #26842)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<literal>NDB Cluster</literal> (Replication): A replicated
unique key allowed duplicate key inserts on the slave. (Bug
#27044)
@@ -473,6 +538,14 @@
<listitem>
<para>
+ A buffer overflow could occur when using
+ <literal>DECIMAL</literal> columns on Windows operating
+ systems. (Bug #28361)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<literal>NDB Cluster</literal>: When an API node sent more
than 1024 signals in a single batch, <literal>NDB</literal>
would process only the first 1024 of these, and then hang.
@@ -987,6 +1060,19 @@
</listitem>
<listitem>
+ <important>
+ <para>
+ When upgrading to MySQL 5.1.18 or later from a previous
+ MySQL version and scheduled events have been used, the
+ upgrade utilities do not accomodate changes in event-related
+ system tables. As a workaround, you can dump events before
+ the upgrade, then restore them from the dump afterwards.
+ This issue was fixed in MySQL 5.1.20 (see Bug #28521).
+ </para>
+ </important>
+ </listitem>
+
+ <listitem>
<para>
The output of <command>mysql <option>--xml</option></command>
and <command>mysqldump <option>--xml</option></command> now
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r6748 - in trunk: refman-5.0 refman-5.1 | jon | 10 Jun |
