Author: paul
Date: 2005-11-01 21:44:51 +0100 (Tue, 01 Nov 2005)
New Revision: 208
Log:
r240@kite-hub: paul | 2005-11-01 14:44:33 -0600
Document bugfixes:
Bug#14009
Bug#14831
Bug#11074
Bug#14027
Bug#14139
Bug#11694
Bug#12839
Bug#14358
Bug#13774
Modified:
trunk/
trunk/refman-common/news-4.1.xml
trunk/refman-common/news-5.0.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:3240
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:235
+ b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:3240
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:240
Modified: trunk/refman-common/news-4.1.xml
===================================================================
--- trunk/refman-common/news-4.1.xml 2005-11-01 16:57:33 UTC (rev 207)
+++ trunk/refman-common/news-4.1.xml 2005-11-01 20:44:51 UTC (rev 208)
@@ -246,6 +246,42 @@
<listitem>
<para>
+ <command>mysqld_safe</command> did not correctly start the
+ <literal>-max</literal> version of the server (if it was
+ present) if the <option>--ledir</option> option was given.
+ (Bug #13774)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The endian byte in for spatial values in WKB format was not
+ consistently respected. (Bug #12839)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ An expression in an <literal>ORDER BY</literal> clause failed
+ with <literal>Unknown column
+ '<replaceable>col_name</replaceable>' in 'order
+ clause'</literal> if the expression referred to a column
+ alias. (Bug #11694)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Statements of the form <literal>CREATE TABLE … SELECT
+ …</literal> that created a column with a multi-byte
+ character set could incorrectly calculate the maximum length
+ of the column, resulting in a <literal>Specified key was too
+ long</literal> error. (Bug #14139)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Use of <literal><replaceable>col_name</replaceable> =
VALUES(<replaceable>col_name</replaceable>)</literal> in the
<literal>ON DUPLICATE KEY UPDATE</literal> clause of an
@@ -287,10 +323,10 @@
<listitem>
<para>
- <literal>ORDER BY
- ABS(<replaceable>expr</replaceable>)</literal> could cause a
- crash if <replaceable>expr</replaceable> was
- <literal>NULL</literal>. (Bug #14009)
+ <literal>TIMEDIFF()</literal>, <literal>ADDTIME()</literal>,
+ and <literal>STR_TO_DATE()</literal> were not reporting that
+ they could return <literal>NULL</literal>, so functions that
+ invoked them might misinterpret their results. (Bug #14009)
</para>
</listitem>
@@ -314,12 +350,8 @@
<para>
<literal>NDB Cluster</literal>: Repeated transactions using
unique index lookups could cause a memory leak leading to
- error 288,
-
- <errortext>Out of index operations in transaction
- coordinator</errortext>
-
- . (Bug #14199)
+ error 288, <literal>Out of index operations in transaction
+ coordinator</literal>. (Bug #14199)
</para>
</listitem>
Modified: trunk/refman-common/news-5.0.xml
===================================================================
--- trunk/refman-common/news-5.0.xml 2005-11-01 16:57:33 UTC (rev 207)
+++ trunk/refman-common/news-5.0.xml 2005-11-01 20:44:51 UTC (rev 208)
@@ -226,6 +226,61 @@
<listitem>
<para>
+ <command>mysqld_safe</command> did not correctly start the
+ <literal>-max</literal> version of the server (if it was
+ present) if the <option>--ledir</option> option was given.
+ (Bug #13774)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The <command>mysql</command> parser did not properly strip the
+ delimiter from input lines less than nine characters long. For
+ example, this could cause <literal>USE abc;</literal> to
+ result in an <literal>Unknown database: abc;</literal> error.
+ (Bug #14358)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Statements of the form <literal>CREATE TABLE … SELECT
+ …</literal> that created a column with a multi-byte
+ character set could incorrectly calculate the maximum length
+ of the column, resulting in a <literal>Specified key was too
+ long</literal> error. (Bug #14139)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Some updatable views could not be updated. (Bug #14027)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Running <literal>OPTIMIZE TABLE</literal> and other
+ data-updating statements concurrently on an
+ <literal>InnoDB</literal> table could cause a crash or the
+ following warnings in the error log: <literal>Warning: Found
+ locks from different threads in write: enter
+ write_lock</literal>, <literal>Warning: Found locks from
+ different threads in write: start of release lock</literal>.
+ (Bug #11704)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Indexes for <literal>BDB</literal> tables were being limited
+ incorrectly to 255 bytes. (Bug #14381)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Use of <literal><replaceable>col_name</replaceable> =
VALUES(<replaceable>col_name</replaceable>)</literal> in the
<literal>ON DUPLICATE KEY UPDATE</literal> clause of an
@@ -294,10 +349,10 @@
<listitem>
<para>
- <literal>ORDER BY
- ABS(<replaceable>expr</replaceable>)</literal> could cause a
- crash if <replaceable>expr</replaceable> was
- <literal>NULL</literal>. (Bug #14009)
+ <literal>TIMEDIFF()</literal>, <literal>ADDTIME()</literal>,
+ and <literal>STR_TO_DATE()</literal> were not reporting that
+ they could return <literal>NULL</literal>, so functions that
+ invoked them might misinterpret their results. (Bug #14009)
</para>
</listitem>
@@ -746,6 +801,16 @@
<listitem>
<para>
+ An expression in an <literal>ORDER BY</literal> clause failed
+ with <literal>Unknown column
+ '<replaceable>col_name</replaceable>' in 'order
+ clause'</literal> if the expression referred to a column
+ alias. (Bug #11694)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<command>mysqldump</command> could not dump views. (Bug
#14061)
</para>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r208 - in trunk: . refman-common | paul | 1 Nov |
