Author: paul
Date: 2006-11-27 20:48:25 +0100 (Mon, 27 Nov 2006)
New Revision: 4045
Log:
r16270@polar: paul | 2006-11-27 13:48:04 -0600
Document bugfixes:
Bug#8663
Bug#11032
Bug#13544
Bug#19491
Bug#23769
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:16265
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:12586
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:11757
+ 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:16270
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:12586
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:11757
Modified: trunk/refman-4.1/news-4.1.xml
===================================================================
--- trunk/refman-4.1/news-4.1.xml 2006-11-27 18:52:29 UTC (rev 4044)
+++ trunk/refman-4.1/news-4.1.xml 2006-11-27 19:48:25 UTC (rev 4045)
Changed blocks: 1, Lines Added: 8, Lines Deleted: 0; 768 bytes
@@ -185,6 +185,14 @@
<listitem>
<para>
+ Metadata for columns calculated from scalar subqueries was
+ limited to integer, double, or string, even if the actual
+ type of the column was different. (Bug #11032)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
For ODBC compatibility, MySQL supports use of <literal>WHERE
<replaceable>col_name</replaceable> IS NULL</literal> for
<literal>DATE</literal> or <literal>DATETIME</literal> columns
Modified: trunk/refman-5.0/releasenotes-es-5.0.xml
===================================================================
--- trunk/refman-5.0/releasenotes-es-5.0.xml 2006-11-27 18:52:29 UTC (rev 4044)
+++ trunk/refman-5.0/releasenotes-es-5.0.xml 2006-11-27 19:48:25 UTC (rev 4045)
Changed blocks: 2, Lines Added: 36, Lines Deleted: 0; 2060 bytes
@@ -63,6 +63,32 @@
<listitem>
<para>
+ For a cast of a <literal>DATETIME</literal> value containing
+ microseconds to <literal>DECIMAL</literal>, the microseconds
+ part was truncated without generating a warning. Now the
+ microseconds part is preserved. (Bug #19491)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Metadata for columns calculated from scalar subqueries was
+ limited to integer, double, or string, even if the actual type
+ of the column was different. (Bug #11032)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The result for <literal>CAST()</literal> when casting a value
+ to <literal>UNSIGNED</literal> was limited to the maximum
+ signed <literal>BIGINT</literal> value, not the maximum
+ unsigned value. (Bug #8663)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Using <literal>EXPLAIN</literal> caused a server crash for
queries that selected from
<literal>INFORMATION_SCHEMA</literal> in a subquery in the
@@ -540,6 +566,16 @@
<listitem>
<para>
+ The internal SQL interpreter of <literal>InnoDB</literal>
+ placed an unnecessary lock on the supremum record when
+ <literal>innodb_locks_unsafe_for_binlog=1</literal>. This
+ caused an assertion failure when <literal>InnoDB</literal> was
+ built with debugging enabled. (Bug #23769)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
If a table contains an <literal>AUTO_INCREMENT</literal>
column, inserting into an insertable view on the table that
does not include the <literal>AUTO_INCREMENT</literal> column
Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml 2006-11-27 18:52:29 UTC (rev 4044)
+++ trunk/refman-5.1/news-5.1.xml 2006-11-27 19:48:25 UTC (rev 4045)
Changed blocks: 2, Lines Added: 34, Lines Deleted: 0; 1854 bytes
@@ -104,6 +104,32 @@
<listitem>
<para>
+ For a cast of a <literal>DATETIME</literal> value containing
+ microseconds to <literal>DECIMAL</literal>, the microseconds
+ part was truncated without generating a warning. Now the
+ microseconds part is preserved. (Bug #19491)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Metadata for columns calculated from scalar subqueries was
+ limited to integer, double, or string, even if the actual type
+ of the column was different. (Bug #11032)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The result for <literal>CAST()</literal> when casting a value
+ to <literal>UNSIGNED</literal> was limited to the maximum
+ signed <literal>BIGINT</literal> value, not the maximum
+ unsigned value. (Bug #8663)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Some unnecessary Valgrind warnings were removed from the
server. (Bug #24488, Bug #24533).
</para>
@@ -1807,6 +1833,14 @@
<listitem>
<para>
+ <literal>InnoDB</literal> locking was improved by removing a
+ gap lock for the case that you try to delete the same row
+ twice within a transaction. (Bug #13544)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Deleting entries from a large <literal>MyISAM</literal> index
could cause index corruption when it needed to shrink. Deletes
from an index can happen when a record is deleted, when a key
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r4045 - in trunk: . refman-4.1 refman-5.0 refman-5.1 | paul | 27 Nov |
