Author: paul
Date: 2007-04-11 04:51:29 +0200 (Wed, 11 Apr 2007)
New Revision: 5821
Log:
r18904@frost: paul | 2007-04-10 21:47:53 -0500
Document bugfixes:
Bug#21976
Bug#23666
Bug#25082
Bug#25927
Bug#26138
Bug#27176
Bug#27229
Bug#27257
Bug#27327
Bug#27532
Bug#27586
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:23095
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:18893
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:14593
+ 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:23095
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:18904
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:14593
Modified: trunk/refman-4.1/news-4.1.xml
===================================================================
--- trunk/refman-4.1/news-4.1.xml 2007-04-11 02:50:18 UTC (rev 5820)
+++ trunk/refman-4.1/news-4.1.xml 2007-04-11 02:51:29 UTC (rev 5821)
Changed blocks: 1, Lines Added: 11, Lines Deleted: 0; 917 bytes
@@ -300,6 +300,17 @@
<listitem>
<para>
+ Incorrect results could be returned for some queries that
+ contained a select list expression with <literal>IN</literal>
+ or <literal>BETWEEN</literal> together with an <literal>ORDER
+ BY</literal> or <literal>GROUP BY</literal> on the same
+ expression using <literal>NOT IN</literal> or <literal>NOT
+ BETWEEN</literal>. (Bug #27532)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<literal>GRANT</literal> statements were not replicated if the
server was started with the
<option>--replicate-ignore-table</option> or
Modified: trunk/refman-5.0/releasenotes-es-5.0.xml
===================================================================
--- trunk/refman-5.0/releasenotes-es-5.0.xml 2007-04-11 02:50:18 UTC (rev 5820)
+++ trunk/refman-5.0/releasenotes-es-5.0.xml 2007-04-11 02:51:29 UTC (rev 5821)
Changed blocks: 2, Lines Added: 82, Lines Deleted: 2; 3472 bytes
@@ -318,6 +318,85 @@
<listitem>
<para>
+ Setting a column to <literal>NOT NULL</literal> with an
+ <literal>ON DELETE SET NULL</literal> clause foreign key
+ crashes the server. (Bug #25927)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The values displayed for the
+ <literal>Innodb_row_lock_time</literal>,
+ <literal>Innodb_row_lock_time_avg</literal>, and
+ <literal>Innodb_row_lock_time_max</literal> status variables
+ were incorrect. (Bug #23666)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>COUNT(<replaceable>decimal_expr</replaceable>)</literal>
+ sometimes generated a spurious truncation warning. (Bug
+ #21976)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ With <literal>NO_AUTO_VALUE_ON_ZERO</literal> SQL mode
+ enabled, <literal>LOAD DATA</literal> operations could assign
+ incorrect <literal>AUTO_INCREMENT</literal> values. (Bug
+ #27586)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Incorrect results could be returned for some queries that
+ contained a select list expression with <literal>IN</literal>
+ or <literal>BETWEEN</literal> together with an <literal>ORDER
+ BY</literal> or <literal>GROUP BY</literal> on the same
+ expression using <literal>NOT IN</literal> or <literal>NOT
+ BETWEEN</literal>. (Bug #27532)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Queries containing subqueries with <literal>COUNT(*)</literal>
+ aggregated in an outer context returned incorrect results.
+ This happened only if the subquery did not contain any
+ references to outer columns. (Bug #27257)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Use of an aggregate function from an outer context as an
+ argument to <literal>GROUP_CONCAT()</literal> caused a server
+ crash. (Bug #27229)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>REPAIR TABLE ... USE_FRM</literal> with an
+ <literal>ARCHIVE</literal> table deleted all records from the
+ table. (Bug #26138)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Restoration of the default database after stored routine or
+ trigger execution on a slave could cause replication to stop
+ if the database no longer existed. (Bug #25082)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
On Windows, debug builds of <command>mysqld</command> could
fail with heap assertions. (Bug #25765)
</para>
@@ -332,8 +411,9 @@
<listitem>
<para>
- String truncation upon insertion into a integer column did not
- generate a warning (or an error in strict mode). (Bug #26359)
+ String truncation upon insertion into an integer or year
+ column did not generate a warning (or an error in strict
+ mode). (Bug #26359, Bug #27176)
</para>
</listitem>
Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml 2007-04-11 02:50:18 UTC (rev 5820)
+++ trunk/refman-5.1/news-5.1.xml 2007-04-11 02:51:29 UTC (rev 5821)
Changed blocks: 1, Lines Added: 84, Lines Deleted: 2; 3574 bytes
@@ -354,13 +354,95 @@
<listitem>
<para>
- String truncation upon insertion into a integer column did not
- generate a warning (or an error in strict mode). (Bug #26359)
+ Setting a column to <literal>NOT NULL</literal> with an
+ <literal>ON DELETE SET NULL</literal> clause foreign key
+ crashes the server. (Bug #25927)
</para>
</listitem>
<listitem>
<para>
+ The values displayed for the
+ <literal>Innodb_row_lock_time</literal>,
+ <literal>Innodb_row_lock_time_avg</literal>, and
+ <literal>Innodb_row_lock_time_max</literal> status variables
+ were incorrect. (Bug #23666)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>COUNT(<replaceable>decimal_expr</replaceable>)</literal>
+ sometimes generated a spurious truncation warning. (Bug
+ #21976)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ With <literal>NO_AUTO_VALUE_ON_ZERO</literal> SQL mode
+ enabled, <literal>LOAD DATA</literal> operations could assign
+ incorrect <literal>AUTO_INCREMENT</literal> values. (Bug
+ #27586)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Incorrect results could be returned for some queries that
+ contained a select list expression with <literal>IN</literal>
+ or <literal>BETWEEN</literal> together with an <literal>ORDER
+ BY</literal> or <literal>GROUP BY</literal> on the same
+ expression using <literal>NOT IN</literal> or <literal>NOT
+ BETWEEN</literal>. (Bug #27532)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ For the <literal>INFORMATION_SCHEMA</literal>
+ <literal>SESSION_STATUS</literal> and
+ <literal>GLOBAL_STATUS</literal> tables, some status values
+ were incorrectly converted to the data type of the
+ <literal>VARIABLE_VALUE</literal> column. (Bug #27327)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Queries containing subqueries with <literal>COUNT(*)</literal>
+ aggregated in an outer context returned incorrect results.
+ This happened only if the subquery did not contain any
+ references to outer columns. (Bug #27257)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Use of an aggregate function from an outer context as an
+ argument to <literal>GROUP_CONCAT()</literal> caused a server
+ crash. (Bug #27229)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Restoration of the default database after stored routine or
+ trigger execution on a slave could cause replication to stop
+ if the database no longer existed. (Bug #25082)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ String truncation upon insertion into an integer or year
+ column did not generate a warning (or an error in strict
+ mode). (Bug #26359, Bug #27176)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
In out-of-memory conditions, the server might crash or
otherwise not report an error to the Windows event log. (Bug
#27490)
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r5821 - in trunk: . refman-4.1 refman-5.0 refman-5.1 | paul | 11 Apr |
