Author: paul
Date: 2006-07-24 20:45:04 +0200 (Mon, 24 Jul 2006)
New Revision: 2818
Log:
r12707@frost: paul | 2006-07-24 13:33:43 -0500
Document bugfixes:
Bug#10946
Bug#16327
Bug#18243
Bug#19714
Bug#20221
Bug#20499
Bug#20519
Bug#20569
Modified:
trunk/refman-common/news-4.1.xml
trunk/refman-common/news-5.0.xml
trunk/refman-common/news-5.1.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:11840
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:12706
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:8441
+ 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:11840
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:12707
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:8441
Modified: trunk/refman-common/news-4.1.xml
===================================================================
--- trunk/refman-common/news-4.1.xml 2006-07-24 18:44:39 UTC (rev 2817)
+++ trunk/refman-common/news-4.1.xml 2006-07-24 18:45:04 UTC (rev 2818)
Changed blocks: 1, Lines Added: 28, Lines Deleted: 3; 1628 bytes
@@ -190,10 +190,35 @@
<listitem>
<para>
+ Multiple invocations of the <literal>REVERSE()</literal>
+ function could return different results. (Bug #18243)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Conversion of <literal>TIMESTAMP</literal> values between UTC
+ and the local time zone resulted in some values having the
+ year 2069 rather than 1969. (Bug #16327)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Using <literal>> ALL</literal> with subqueries that return
+ no rows yielded incorrect results under certain circumstances
+ due to incorrect application of <literal>MIN()/MAX()</literal>
+ optimization. (Bug #18503)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Using <literal>ANY</literal> with <quote>non-table</quote>
- subqueries such as <literal>SELECT 1</literal> yields results
- under certain circumstances due to incorrect application of
- <literal>MIN()/MAX()</literal> optimization. (Bug #16302)
+ subqueries such as <literal>SELECT 1</literal> yielded
+ incorrect results under certain circumstances due to incorrect
+ application of <literal>MIN()/MAX()</literal> optimization.
+ (Bug #16302)
</para>
</listitem>
Modified: trunk/refman-common/news-5.0.xml
===================================================================
--- trunk/refman-common/news-5.0.xml 2006-07-24 18:44:39 UTC (rev 2817)
+++ trunk/refman-common/news-5.0.xml 2006-07-24 18:45:04 UTC (rev 2818)
Changed blocks: 2, Lines Added: 63, Lines Deleted: 3; 3045 bytes
@@ -344,10 +344,62 @@
<listitem>
<para>
+ The same trigger error message was produced under two
+ conditions: The trigger duplicated an existing trigger name,
+ or the trigger duplicated an existing combination of action
+ and event. Now different messages are produced for the two
+ conditions so as to be more informative. (Bug #10946)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Multiplication of <literal>DECIMAL</literal> values could
+ produce incorrect fractional part and trailing garbage caused
+ by signed overflow. (Bug #20569)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A subquery that contained <literal>LIMIT
+ <replaceable>N</replaceable>,1</literal> could return more
+ than one row. (Bug #20519)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>DESCRIBE</literal> returned the type
+ <literal>BIGINT</literal> for a column of a view if the column
+ was specified by an expression over values of the type
+ <literal>INT</literal>. (Bug #19714)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Multiple invocations of the <literal>REVERSE()</literal>
+ function could return different results. (Bug #18243)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Using <literal>> ALL</literal> with subqueries that return
+ no rows yielded incorrect results under certain circumstances
+ due to incorrect application of <literal>MIN()/MAX()</literal>
+ optimization. (Bug #18503)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Using <literal>ANY</literal> with <quote>non-table</quote>
- subqueries such as <literal>SELECT 1</literal> yields results
- under certain circumstances due to incorrect application of
- <literal>MIN()/MAX()</literal> optimization. (Bug #16302)
+ subqueries such as <literal>SELECT 1</literal> yielded
+ incorrect results under certain circumstances due to incorrect
+ application of <literal>MIN()/MAX()</literal> optimization.
+ (Bug #16302)
</para>
</listitem>
@@ -618,6 +670,14 @@
<listitem>
<para>
+ <command>mysqldump</command> produced a malformed dump file
+ when dumping multiple databases that contained views. (Bug
+ #20221)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<literal>SELECT @@INSERT_ID</literal> displayed a value
unrelated to a preceding <literal>SET INSERT_ID</literal>. (It
was returning <literal>LAST_INSERT_ID</literal> instead.) (Bug
Modified: trunk/refman-common/news-5.1.xml
===================================================================
--- trunk/refman-common/news-5.1.xml 2006-07-24 18:44:39 UTC (rev 2817)
+++ trunk/refman-common/news-5.1.xml 2006-07-24 18:45:04 UTC (rev 2818)
Changed blocks: 1, Lines Added: 21, Lines Deleted: 0; 1296 bytes
@@ -320,6 +320,27 @@
<listitem>
<para>
+ The same trigger error message was produced under two
+ conditions: The trigger duplicated an existing trigger name,
+ or the trigger duplicated an existing combination of action
+ and event. Now different messages are produced for the two
+ conditions so as to be more informative. (Bug #10946)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ In mixed binary logging mode, storing into a temporary table a
+ row that uses a function that causes a switch to row-based
+ binary logging, the temporary table's data was not logged.
+ Consequently, selecting from the table into a non-temporary
+ table would would work on the master but not the slave. (Bug
+ #20499)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Re-executing a stored procedure with a complex stored
procedure cursor query could lead to a server crash. (Bug
#15217)
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r2818 - in trunk: . refman-common | paul | 24 Jul |
