Author: jstephens
Date: 2006-02-14 11:30:45 +0100 (Tue, 14 Feb 2006)
New Revision: 1307
Log:
Documented Cluster bugfixes:
13965, 13966, 16481, 16872, 17005, 17081,
17087, 17154, 17108, 17206, 17235,
17295, 17249, 12757, 17325, 17340
Documented Partitioning bugfix: 17179
Updated 5.1.6 tag date for release.
Modified:
trunk/refman-common/news-4.1.xml
trunk/refman-common/news-5.0.xml
trunk/refman-common/news-5.1.xml
trunk/refman-common/titles.en.ent
Modified: trunk/refman-common/news-4.1.xml
===================================================================
--- trunk/refman-common/news-4.1.xml 2006-02-14 03:34:48 UTC (rev 1306)
+++ trunk/refman-common/news-4.1.xml 2006-02-14 10:30:45 UTC (rev 1307)
@@ -168,11 +168,12 @@
<listitem>
<para>
- InnoDB now caches a list of unflushed files instead of
- scanning for unflushed files during a table flush operation.
- This improves performance when
- <literal>--innodb-file-per-table</literal> is set on a system
- with a large number of InnoDB tables. (Bug #15653)
+ <literal>InnoDB</literal> now caches a list of unflushed files
+ instead of scanning for unflushed files during a table flush
+ operation. This improves performance when
+ <option>--innodb-file-per-table</option> is set on a system
+ with a large number of <literal>InnoDB</literal> tables. (Bug
+ #15653)
</para>
</listitem>
@@ -183,6 +184,56 @@
</para>
<itemizedlist>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: An <literal>UPDATE</literal>
+ with an inner join failed to match any records if both tables
+ in the join did not have a primary key. (Bug #17257)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: A <literal>DELETE</literal>
+ with a join in the <literal>WHERE</literal> clause failed to
+ retrieve any records if both tables in the join did not have a
+ primary key. (Bug #17249)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: In some cases, <literal>LOAD
+ DATA INFILE</literal> did not load all data into
+ <literal>NDB</literal> tables. (Bug #17081)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: The <literal>REDO</literal>
+ log would become corrupted (and thus unreadable) in some
+ circumstances, due to a failure in the query handler. (Bug
+ #17295)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: No error message was generated
+ for setting <literal>NoOfFragmentLogFiles</literal> too low.
+ (Bug #13966)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: No error message was generated
+ for setting <literal>MaxNoOfAttributes</literal> too low. (Bug
+ #13965)
+ </para>
+ </listitem>
<listitem>
<para>
Modified: trunk/refman-common/news-5.0.xml
===================================================================
--- trunk/refman-common/news-5.0.xml 2006-02-14 03:34:48 UTC (rev 1306)
+++ trunk/refman-common/news-5.0.xml 2006-02-14 10:30:45 UTC (rev 1307)
@@ -291,6 +291,73 @@
</para>
<itemizedlist>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: Following multiple forced
+ shutdowns and restarts of data nodes, <literal>DROP
+ DATABASE</literal> could fail. (Bug #17325)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: An <literal>UPDATE</literal>
+ with an inner join failed to match any records if both tables
+ in the join did not have a primary key. (Bug #17257)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: A <literal>DELETE</literal>
+ with a join in the <literal>WHERE</literal> clause failed to
+ retrieve any records if both tables in the join did not have a
+ primary key. (Bug #17249)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The error message returned by <literal>perror
+ <option>--ndb</option></literal> was prefixed with
+ <errortext>OS error code:</errortext> instead of
+ <errortext>NDB error code:</errortext>. (Bug #17235)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: In some cases, <literal>LOAD
+ DATA INFILE</literal> did not load all data into
+ <literal>NDB</literal> tables. (Bug #17081)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: The <literal>REDO</literal>
+ log would become corrupted (and thus unreadable) in some
+ circumstances, due to a failure in the query handler. (Bug
+ #17295)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: No error message was generated
+ for setting <literal>NoOfFragmentLogFiles</literal> too low.
+ (Bug #13966)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: No error message was generated
+ for setting <literal>MaxNoOfAttributes</literal> too low. (Bug
+ #13965)
+ </para>
+ </listitem>
<listitem>
<para>
@@ -310,15 +377,15 @@
<listitem>
<para>
- The <literal>SELECT</literal> privilege was being required
- even for triggers that performed no selects. (Bug #15196)
+ The <literal>SELECT</literal> privilege was required for
+ triggers that performed no selects. (Bug #15196)
</para>
</listitem>
<listitem>
<para>
- The <literal>UPDATE</literal> privilege was being required
- even for triggers that performed no updates. (Bug #15166)
+ The <literal>UPDATE</literal> privilege was required for
+ triggers that performed no updates. (Bug #15166)
</para>
</listitem>
Modified: trunk/refman-common/news-5.1.xml
===================================================================
--- trunk/refman-common/news-5.1.xml 2006-02-14 03:34:48 UTC (rev 1306)
+++ trunk/refman-common/news-5.1.xml 2006-02-14 10:30:45 UTC (rev 1307)
@@ -66,6 +66,15 @@
</para>
<itemizedlist>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: Attempting to <literal>SELECT
+ ... FROM INFORMATION_SCHEMA.FILES</literal> now raises a
+ warning in the event that the cluster has crashed. (Bug
+ #17087)
+ </para>
+ </listitem>
<listitem>
<para>
@@ -88,18 +97,141 @@
</para>
<itemizedlist>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: <literal>SHOW CREATE
+ TABLE</literal> would fail when run against a table created
+ in a different session. (Bug #17340)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: Following multiple forced
+ shutdowns and restarts of data nodes, <literal>DROP
+ DATABASE</literal> could fail. (Bug #17325)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: An <literal>UPDATE</literal>
+ with an inner join failed to match any records if both tables
+ in the join did not have a primary key. (Bug #17257)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: A <literal>DELETE</literal>
+ with a join in the <literal>WHERE</literal> clause failed to
+ retrieve any records if both tables in the join did not have a
+ primary key. (Bug #17249)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The <literal>NDB Cluster</literal> storage engine did not
+ allow views to be updated. (Bug #17206)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: Row-based replication of a
+ cluster failed to take <option>--binlog_ignore_db
+ settings</option> into account. (Bug #17188)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Trying to create a partitioned table with more than 32
+ attributes failed. (Bug #17179)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: When attempting to import data
+ into an <literal>NDB</literal> table using <literal>LOAD DATA
+ INFILE</literal>, the server would hang in the event of a
+ duplicate key error. (Bug #17154)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: In some cases, <literal>LOAD
+ DATA INFILE</literal> did not load all data into
+ <literal>NDB</literal> tables. (Bug #17081)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: Performing large numbers of
+ data manipulation statements on cluster tables using Disk Data
+ could lead to a server crash. ()
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: In some cases, a cluster using
+ Disk Data tables could not be restarted following a normal
+ shutdown. (Bug #16872)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: The <literal>REDO</literal>
+ log would become corrupted (and thus unreadable) in some
+ circumstances, due to a failure in the query handler. (Bug
+ #17295)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: <literal>CREATE TABLE
+ <replaceable>new_tbl</replaceable> LIKE
+ <replaceable>old_tbl</replaceable>;</literal> failed when
+ <replaceable>old_tbl</replaceable> used the
+ <literal>NDB</literal> storage engine. (Bug #17005)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: No error message was generated
+ for setting <literal>NoOfFragmentLogFiles</literal> too low.
+ (Bug #13966)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: No error message was generated
+ for setting <literal>MaxNoOfAttributes</literal> too low. (Bug
+ #13965)
+ </para>
+ </listitem>
<listitem>
<para>
- The <literal>SELECT</literal> privilege was being required
- even for triggers that performed no selects. (Bug #15196)
+ The <literal>SELECT</literal> privilege was required for
+ triggers that performed no selects. (Bug #15196)
</para>
</listitem>
<listitem>
<para>
- The <literal>UPDATE</literal> privilege was being required
- even for triggers that performed no updates. (Bug #15166)
+ The <literal>UPDATE</literal> privilege was required for
+ triggers that performed no updates. (Bug #15166)
</para>
</listitem>
Modified: trunk/refman-common/titles.en.ent
===================================================================
--- trunk/refman-common/titles.en.ent 2006-02-14 03:34:48 UTC (rev 1306)
+++ trunk/refman-common/titles.en.ent 2006-02-14 10:30:45 UTC (rev 1307)
@@ -1267,7 +1267,7 @@
<!ENTITY title-news-5-1-3 "Changes in release 5.1.3 (29 November 2005)">
<!ENTITY title-news-5-1-4 "Changes in release 5.1.4 (21 December 2005)">
<!ENTITY title-news-5-1-5 "Changes in release 5.1.5 (10 January 2006)">
-<!ENTITY title-news-5-1-6 "Changes in release 5.1.6 (Not yet released)">
+<!ENTITY title-news-5-1-6 "Changes in release 5.1.6 (01 February 2006)">
<!ENTITY title-news-5-1-7 "Changes in release 5.1.7 (Not yet released)">
<!ENTITY title-news-5-1-x "Changes in release 5.1.x (Development)">
<!ENTITY title-no-matching-rows "Solving Problems with No Matching Rows">
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r1307 - trunk/refman-common | jon | 14 Feb |
