Author: paul
Date: 2007-02-26 22:02:58 +0100 (Mon, 26 Feb 2007)
New Revision: 5071
Log:
r20544@polar: paul | 2007-02-26 14:58:55 -0600
Document bugfixes:
Bug#10798
Bug#12122
Bug#20691
Bug#22533
Bug#23170
Bug#23938
Bug#25931
Bug#26209
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:20537
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:16743
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:20544
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:16743
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-02-26 21:01:27 UTC (rev 5070)
+++ trunk/refman-4.1/news-4.1.xml 2007-02-26 21:02:58 UTC (rev 5071)
Changed blocks: 1, Lines Added: 26, Lines Deleted: 0; 1310 bytes
@@ -260,6 +260,32 @@
<listitem>
<para>
+ Storing values specified as hexadecimal values 64 or more bits
+ long into <literal>BIGINT</literal> or <literal>BIGINT
+ UNSIGNED</literal> columns did not raise any warning or error
+ if the value was out of range. (Bug #22533)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>ISNULL(DATE(NULL))</literal> and
+ <literal>ISNULL(CAST(NULL AS DATE))</literal> erroneously
+ returned false. (Bug #23938)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ If a slave server closed its relay log (for example, due to an
+ error during log rotation), the I/O thread did not recognize
+ this and still tried to write to the log, causing a server
+ crash. (Bug #10798)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Foreign key identifiers for <literal>InnoDB</literal> tables
could not contain certain characters. (Bug #24299)
</para>
Modified: trunk/refman-5.0/releasenotes-es-5.0.xml
===================================================================
--- trunk/refman-5.0/releasenotes-es-5.0.xml 2007-02-26 21:01:27 UTC (rev 5070)
+++ trunk/refman-5.0/releasenotes-es-5.0.xml 2007-02-26 21:02:58 UTC (rev 5071)
Changed blocks: 2, Lines Added: 71, Lines Deleted: 9; 3549 bytes
@@ -257,6 +257,77 @@
<listitem>
<para>
+ The <literal>WITH CHECK OPTION</literal> clause for views was
+ ignored for updates of multiple-table views when the updates
+ could not be performed on fly and the rows to update had to be
+ put into temporary tables first. (Bug #25931)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Using <literal>ORDER BY</literal> or <literal>GROUP
+ BY</literal> could yield different results when selecting from
+ a view and selecting from the underlying table. (Bug #26209)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>LAST_INSERT_ID()</literal> was not reset to 0 if
+ <literal>INSERT ... SELECT</literal> inserted no rows. (Bug
+ #23170)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Storing values specified as hexadecimal values 64 or more bits
+ long into <literal>BIT(64)</literal>,
+ <literal>BIGINT</literal>, or <literal>BIGINT
+ UNSIGNED</literal> columns did not raise any warning or error
+ if the value was out of range. (Bug #22533)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Inserting <literal>DEFAULT</literal> into a column with no
+ default value could result in garbage in the column. Now the
+ same result occurs as when inserting <literal>NULL</literal>
+ into a <literal>NOT NULL</literal> column. (Bug #20691)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The presence of <literal>ORDER BY</literal> in a view
+ definition prevented the <literal>MERGE</literal> algorithm
+ from being used to resolve the view even if nothing else in
+ the definition required the <literal>TEMPTABLE</literal>
+ algorithm. (Bug #12122)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>ISNULL(DATE(NULL))</literal> and
+ <literal>ISNULL(CAST(NULL AS DATE))</literal> erroneously
+ returned false. (Bug #23938)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ If a slave server closed its relay log (for example, due to an
+ error during log rotation), the I/O thread did not recognize
+ this and still tried to write to the log, causing a server
+ crash. (Bug #10798)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Using an <literal>INFORMATION_SCHEMA</literal> table with
<literal>ORDER BY</literal> in a subquery could cause a server
crash. (Bug #24630)
@@ -1797,15 +1868,6 @@
<listitem>
<para>
- Inserting <literal>DEFAULT</literal> into a column with no
- default value could result in garbage in the column. Now the
- same result occurs as when inserting <literal>NULL</literal>
- into a <literal>NOT NULL</literal> column. (Bug #20691)
- </para>
- </listitem>
-
- <listitem>
- <para>
<filename>mysql_fix_privilege_tables.sql</filename> altered
the <literal>table_privs.table_priv</literal> column to
contain too few privileges, causing loss of the
Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml 2007-02-26 21:01:27 UTC (rev 5070)
+++ trunk/refman-5.1/news-5.1.xml 2007-02-26 21:02:58 UTC (rev 5071)
Changed blocks: 2, Lines Added: 63, Lines Deleted: 9; 3293 bytes
@@ -363,6 +363,69 @@
<listitem>
<para>
+ The <literal>WITH CHECK OPTION</literal> clause for views was
+ ignored for updates of multiple-table views when the updates
+ could not be performed on fly and the rows to update had to be
+ put into temporary tables first. (Bug #25931)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Using <literal>ORDER BY</literal> or <literal>GROUP
+ BY</literal> could yield different results when selecting from
+ a view and selecting from the underlying table. (Bug #26209)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Storing values specified as hexadecimal values 64 or more bits
+ long into <literal>BIT(64)</literal>,
+ <literal>BIGINT</literal>, or <literal>BIGINT
+ UNSIGNED</literal> columns did not raise any warning or error
+ if the value was out of range. (Bug #22533)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Inserting <literal>DEFAULT</literal> into a column with no
+ default value could result in garbage in the column. Now the
+ same result occurs as when inserting <literal>NULL</literal>
+ into a <literal>NOT NULL</literal> column. (Bug #20691)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The presence of <literal>ORDER BY</literal> in a view
+ definition prevented the <literal>MERGE</literal> algorithm
+ from being used to resolve the view even if nothing else in
+ the definition required the <literal>TEMPTABLE</literal>
+ algorithm. (Bug #12122)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>ISNULL(DATE(NULL))</literal> and
+ <literal>ISNULL(CAST(NULL AS DATE))</literal> erroneously
+ returned false. (Bug #23938)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ If a slave server closed its relay log (for example, due to an
+ error during log rotation), the I/O thread did not recognize
+ this and still tried to write to the log, causing a server
+ crash. (Bug #10798)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Using an <literal>INFORMATION_SCHEMA</literal> table with
<literal>ORDER BY</literal> in a subquery could cause a server
crash. (Bug #24630)
@@ -2153,15 +2216,6 @@
<listitem>
<para>
- Inserting <literal>DEFAULT</literal> into a column with no
- default value could result in garbage in the column. Now the
- same result occurs as when inserting <literal>NULL</literal>
- into a <literal>NOT NULL</literal> column. (Bug #20691)
- </para>
- </listitem>
-
- <listitem>
- <para>
<filename>mysql_fix_privilege_tables.sql</filename> altered
the <literal>table_privs.table_priv</literal> column to
contain too few privileges, causing loss of the
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r5071 - in trunk: . refman-4.1 refman-5.0 refman-5.1 | paul | 26 Feb |
