Author: paul
Date: 2006-04-11 05:42:58 +0200 (Tue, 11 Apr 2006)
New Revision: 1785
Log:
r9363@frost: paul | 2006-04-10 22:32:56 -0500
Document bugfixes:
Bug#15650
Bug#15758
Bug#15846
Bug#16240
Bug#17126
Bug#18077
Bug#18238
Bug#18252
Bug#18384
Bug#18477
Modified:
trunk/
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:6548
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:9357
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:4334
+ 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:6548
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:9363
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:4334
Modified: trunk/refman-common/news-4.1.xml
===================================================================
--- trunk/refman-common/news-4.1.xml 2006-04-11 03:42:41 UTC (rev 1784)
+++ trunk/refman-common/news-4.1.xml 2006-04-11 03:42:58 UTC (rev 1785)
@@ -190,33 +190,40 @@
</para>
<itemizedlist>
-
+
<listitem>
<para>
+ The <literal>mysql_close()</literal> C API function leaked
+ handles for share-memory connections on Windows. (Bug #15846)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
The euro sign (<literal>€</literal>) was not stored
correctly in columns using the
<literal>latin1_german1_ci</literal> or
<literal>latin1_general_ci</literal> collation. (Bug #18321)
</para>
</listitem>
-
+
<listitem>
<para>
The server was always built as though
<option>--with-extra-charsets=complex</option> had been
- specified. (Bug #12076)
+ specified. (Bug #12076)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>SELECT ... WHERE <replaceable>column</replaceable>
- LIKE 'A%'</literal> when <replaceable>column</replaceable>
- had a key and used the <literal>latin2_czech_cs</literal>
+ LIKE 'A%'</literal> when <replaceable>column</replaceable> had
+ a key and used the <literal>latin2_czech_cs</literal>
collation. (Bug #17374)
</para>
</listitem>
-
+
<listitem>
<para>
A query using WHERE (<replaceable>column_1</replaceable>,
Modified: trunk/refman-common/news-5.0.xml
===================================================================
--- trunk/refman-common/news-5.0.xml 2006-04-11 03:42:41 UTC (rev 1784)
+++ trunk/refman-common/news-5.0.xml 2006-04-11 03:42:58 UTC (rev 1785)
@@ -214,6 +214,33 @@
<listitem>
<para>
+ <literal>DELETE</literal> with <literal>LEFT JOIN</literal>
+ for <literal>InnoDB</literal> tables could crash the server if
+ <literal>innodb_locks_unsafe_for_binlog</literal> was enabled.
+ (Bug #15650)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>InnoDB</literal> failure to release an adaptive hash
+ index latch could cause a server crash if the query cache was
+ enabled. (Bug #15758)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ For <command>mysql.server</command>, if the
+ <option>basedir</option> option was specified after
+ <option>datadir</option> in an option file, the setting for
+ <literal>datadir</literal> was ignored and assumed to be
+ located under <literal>basedir</literal>. (Bug #16240)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
The euro sign (<literal>€</literal>) was not stored
correctly in columns using the
<literal>latin1_german1_ci</literal> or
@@ -398,6 +425,49 @@
<listitem>
<para>
+ The <literal>mysql_close()</literal> C API function leaked
+ handles for share-memory connections on Windows. (Bug #15846)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ If <literal>InnoDB</literal> ran out of buffer space for row
+ locks and adaptive hashes, the server would crash. Now
+ <literal>InnoDB</literal> rolls back the transaction. (Bug
+ #18238)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>InnoDB</literal> tables with an adaptive hash blocked
+ other queries during <literal>CHECK TABLE</literal> statements
+ while the entire hash was checked. This could be a long time
+ for a large hash. (Bug #17126)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ For <literal>InnoDB</literal> tables created in MySQL 4.1 or
+ earlier, or created in 5.0 or later with compact format,
+ updating a row so that a long column is updated or the length
+ of some column changes, <literal>InnoDB</literal> later would
+ fail to reclaim the <literal>BLOB</literal> storage space if
+ the row was deleted. (Bug #18252)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>InnoDB</literal> had a memory leak for duplicate-key
+ errors with tables having 90 columns or more. (Bug #18384)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Checks for permissions on database operations could be
performed in a case-insensitive manner (a user with
permissions on database <literal>MYDATABASE</literal> could by
Modified: trunk/refman-common/news-5.1.xml
===================================================================
--- trunk/refman-common/news-5.1.xml 2006-04-11 03:42:41 UTC (rev 1784)
+++ trunk/refman-common/news-5.1.xml 2006-04-11 03:42:58 UTC (rev 1785)
@@ -91,6 +91,14 @@
<listitem>
<para>
+ <literal>InnoDB</literal> failure to release an adaptive hash
+ index latch could cause a server crash if the query cache was
+ enabled. (Bug #15758)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<literal>InnoDB</literal>: <literal>ALTER TABLE</literal> to
add or drop a foreign key for an <literal>InnoDB</literal>
table had no effect. (Bug #18477)
@@ -219,6 +227,16 @@
<listitem>
<para>
+ For <command>mysql.server</command>, if the
+ <option>basedir</option> option was specified after
+ <option>datadir</option> in an option file, the setting for
+ <literal>datadir</literal> was ignored and assumed to be
+ located under <literal>basedir</literal>. (Bug #16240)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
For full-text searches in boolean mode, and when a full-text
parser plugin was used, a
<literal>MYSQL_FTPARSER_PARAM::ftparser_state</literal> could
@@ -826,6 +844,13 @@
<listitem>
<para>
+ The <literal>mysql_close()</literal> C API function leaked
+ handles for share-memory connections on Windows. (Bug #15846)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Checks for permissions on database operations could be
performed in a case-insensitive manner (a user with
permissions on database <literal>MYDATABASE</literal> could by
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r1785 - in trunk: . refman-common | paul | 11 Apr |
