Author: shinz
Date: 2006-03-27 15:48:57 +0200 (Mon, 27 Mar 2006)
New Revision: 1684
Log:
Add 5.1.7 changelog item (closing WL#3023)
Modified:
trunk/refman-common/news-5.1.xml
Modified: trunk/refman-common/news-5.1.xml
===================================================================
--- trunk/refman-common/news-5.1.xml 2006-03-27 13:33:47 UTC (rev 1683)
+++ trunk/refman-common/news-5.1.xml 2006-03-27 13:48:57 UTC (rev 1684)
@@ -31,7 +31,7 @@
<filename>TEMPLATE.news.xml</filename> template in the
<filename>refman-common</filename> directory.
</remark>
-
+
<section id="news-5-1-9">
<title>&title-news-5-1-9;</title>
@@ -214,26 +214,27 @@
<xref linkend="partitioning-handling-nulls"/>. (Bug #15447)
</para>
</listitem>
-
+
<listitem>
<para>
- <emphasis role="bold">Incompatible Change</emphasis>: The semantics of
- <literal>ALTER TABLE <replaceable>t</replaceable>
- ENGINE=<replaceable>X</replaceable>;</literal> for partitioned
- tables is changed, and now means that the storage engine used for
- table <replaceable>t</replaceable> is changed to
+ <emphasis role="bold">Incompatible Change</emphasis>: The
+ semantics of <literal>ALTER TABLE <replaceable>t</replaceable>
+ ENGINE=<replaceable>X</replaceable>;</literal> for partitioned
+ tables is changed, and now means that the storage engine used
+ for table <replaceable>t</replaceable> is changed to
<replaceable>X</replaceable>.
</para>
-
- <para>
- The previous statement formerly (prior to MySQL 5.1.8) meant that all
- partitioning was removed from the table. In order to remove the
- partitioning of a table, the syntax <literal>ALTER TABLE
- <replaceable>t</replaceable> REMOVE PARTITIONING;</literal> is
- introduced. The <literal>REMOVE PARTITIONING</literal> option can be
- used in combination with existing <literal>ALTER TABLE</literal>
- options such as those employed for adding or dropping columns or
- indexes. (Bug #17754)
+
+ <para>
+ The previous statement formerly (prior to MySQL 5.1.8) meant
+ that all partitioning was removed from the table. In order to
+ remove the partitioning of a table, the syntax <literal>ALTER
+ TABLE <replaceable>t</replaceable> REMOVE
+ PARTITIONING;</literal> is introduced. The <literal>REMOVE
+ PARTITIONING</literal> option can be used in combination with
+ existing <literal>ALTER TABLE</literal> options such as those
+ employed for adding or dropping columns or indexes. (Bug
+ #17754)
</para>
</listitem>
@@ -472,58 +473,58 @@
</para>
<itemizedlist>
-
+
<listitem>
<para>
Using triggers with partitioned InnoDB tables led to incorrect
results. (Bug #17744)
</para>
</listitem>
-
+
<listitem>
<para>
Calling <literal>CREATE TABLE</literal> or <literal>ALTER
- TABLE</literal> twice on a partitioned table in a stored procedure
- or a prepared statement resulted in errors and sometimes server
- crashes. (Bug #17290)
+ TABLE</literal> twice on a partitioned table in a stored
+ procedure or a prepared statement resulted in errors and
+ sometimes server crashes. (Bug #17290)
</para>
</listitem>
-
+
<listitem>
<para>
- A problem with <literal>NULL</literal>s and interval mapping sometimes
- caused incorrect results or crashes when trying to use less-than
- searches on partitioned tables. (Bug #17173)
+ A problem with <literal>NULL</literal>s and interval mapping
+ sometimes caused incorrect results or crashes when trying to
+ use less-than searches on partitioned tables. (Bug #17173)
</para>
</listitem>
-
+
<listitem>
<para>
- <literal>CREATE TABLE ... PARTITION ... AS SELECT ...</literal> would
- cause the server to crash. (Bug #15336)
+ <literal>CREATE TABLE ... PARTITION ... AS SELECT
+ ...</literal> would cause the server to crash. (Bug #15336)
</para>
</listitem>
-
+
<listitem>
<para>
- Creating a partition which depends on an expression containing a
- column using the UTF8 character set would cause the server to crash.
- (Bug #14367)
+ Creating a partition which depends on an expression containing
+ a column using the UTF8 character set would cause the server
+ to crash. (Bug #14367)
</para>
</listitem>
-
+
<listitem>
<para>
Invoking more than once a prepared statement that creates a
partitioned table would crash the server. (Bug #14350)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: A <literal>SELECT ... ORDER
- BY</literal> query on an explicitly partitioned Cluster table with
- no explicit indexes would crash the server. (Bug #17899)
+ BY</literal> query on an explicitly partitioned Cluster table
+ with no explicit indexes would crash the server. (Bug #17899)
</para>
</listitem>
@@ -1379,6 +1380,17 @@
</para>
</listitem>
+ <listitem>
+ <para>
+ In row-based replication, when executing a Rows_log_event, the
+ associated table was locked, the rows applied and the lock
+ released. This did not work since there are storage engines
+ that count locks and perform an autocommit when the number of
+ locks reach zero. Now we ensure that all table maps come
+ before all <literal>ROWS</literal> events in a statement.
+ </para>
+ </listitem>
+
</itemizedlist>
<para>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r1684 - trunk/refman-common | stefan | 27 Mar |
