Author: paul
Date: 2007-03-16 18:04:17 +0100 (Fri, 16 Mar 2007)
New Revision: 5420
Log:
r17861@frost: paul | 2007-03-16 12:02:42 -0500
Document bugfixes:
Bug#21103
Bug#25122
Bug#25376
Bug#25966
Modified:
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:21582
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:17796
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:21582
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:17861
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:14593
Modified: trunk/refman-5.0/releasenotes-es-5.0.xml
===================================================================
--- trunk/refman-5.0/releasenotes-es-5.0.xml 2007-03-16 16:00:17 UTC (rev 5419)
+++ trunk/refman-5.0/releasenotes-es-5.0.xml 2007-03-16 17:04:17 UTC (rev 5420)
Changed blocks: 1, Lines Added: 46, Lines Deleted: 0; 2400 bytes
@@ -164,6 +164,52 @@
<listitem>
<para>
+ If a thread previously serviced a connection that was killed,
+ excessive memory and CPU use by the thread occurred if it later
+ serviced a connection that had to wait for a table lock. (Bug
+ #25966)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>CURDATE()</literal> is less than
+ <literal>NOW()</literal>, either when comparing
+ <literal>CURDATE()</literal> directly (<literal>CURDATE() <
+ NOW()</literal> is true) or when casting
+ <literal>CURDATE()</literal> to <literal>DATE</literal>
+ (<literal>CAST(CURDATE() AS DATE) < NOW()</literal> is
+ true). However, storing <literal>CURDATE()</literal> in a
+ <literal>DATE</literal> column and comparing
+ <literal><replaceable>col_name</replaceable> <
+ NOW()</literal> incorrectly yielded false. This is fixed by
+ comparing a <literal>DATE</literal> column as
+ <literal>DATETIME</literal> for comparisons to a
+ <literal>DATETIME</literal> constant. (Bug #21103)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A view on a join is insertable for <literal>INSERT</literal>
+ statements that store values into only one table of the join.
+ However, inserts were being rejected if the inserted-into
+ table was used in a self-join because MySQL incorrectly was
+ considering the insert to modify multiple tables of the view.
+ (Bug #25122)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Expressions involving <literal>SUM()</literal>, when used in
+ an <literal>ORDER BY</literal> clause, could lead to
+ out-of-order results. (Bug #25376)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<literal>LOAD DATA INFILE</literal> sent an okay to the client
before writing the binary log and committing the changes to
the table had finished, thus violating ACID requirements. (Bug
Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml 2007-03-16 16:00:17 UTC (rev 5419)
+++ trunk/refman-5.1/news-5.1.xml 2007-03-16 17:04:17 UTC (rev 5420)
Changed blocks: 1, Lines Added: 46, Lines Deleted: 0; 2367 bytes
@@ -241,6 +241,52 @@
<listitem>
<para>
+ If a thread previously serviced a connection that was killed,
+ excessive memory and CPU use by the thread occurred if it later
+ serviced a connection that had to wait for a table lock. (Bug
+ #25966)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>CURDATE()</literal> is less than
+ <literal>NOW()</literal>, either when comparing
+ <literal>CURDATE()</literal> directly (<literal>CURDATE() <
+ NOW()</literal> is true) or when casting
+ <literal>CURDATE()</literal> to <literal>DATE</literal>
+ (<literal>CAST(CURDATE() AS DATE) < NOW()</literal> is
+ true). However, storing <literal>CURDATE()</literal> in a
+ <literal>DATE</literal> column and comparing
+ <literal><replaceable>col_name</replaceable> <
+ NOW()</literal> incorrectly yielded false. This is fixed by
+ comparing a <literal>DATE</literal> column as
+ <literal>DATETIME</literal> for comparisons to a
+ <literal>DATETIME</literal> constant. (Bug #21103)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A view on a join is insertable for <literal>INSERT</literal>
+ statements that store values into only one table of the join.
+ However, inserts were being rejected if the inserted-into
+ table was used in a self-join because MySQL incorrectly was
+ considering the insert to modify multiple tables of the view.
+ (Bug #25122)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Expressions involving <literal>SUM()</literal>, when used in
+ an <literal>ORDER BY</literal> clause, could lead to
+ out-of-order results. (Bug #25376)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<literal>LOAD DATA INFILE</literal> sent an okay to the client
before writing the binary log and committing the changes to
the table had finished, thus violating ACID requirements. (Bug
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r5420 - in trunk: . refman-5.0 refman-5.1 | paul | 16 Mar |