| List: | Commits | « Previous MessageNext Message » | |
| From: | paul | Date: | April 6 2006 2:35am |
| Subject: | svn commit - mysqldoc@docsrva: r1739 - in trunk: . refman-common | ||
| View as plain text | |||
Author: paul Date: 2006-04-06 02:35:42 +0200 (Thu, 06 Apr 2006) New Revision: 1739 Log: r9272@frost: paul | 2006-04-05 19:34:28 -0500 Document bugfixes: Bug#18116 Bug#18279 Bug#16281 Modified: trunk/ trunk/refman-common/news-5.0.xml trunk/refman-common/news-5.1.xml Property changes on: trunk ___________________________________________________________________ Name: svk:merge - b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:9239 bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:4318 + b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:9272 bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:4318 Modified: trunk/refman-common/news-5.0.xml =================================================================== --- trunk/refman-common/news-5.0.xml 2006-04-05 22:04:43 UTC (rev 1738) +++ trunk/refman-common/news-5.0.xml 2006-04-06 00:35:42 UTC (rev 1739) @@ -186,12 +186,12 @@ please see <ulink url="http://www.mysql.com/network/advisors.html"/>. </para> - + <remark role="todo"> Uncomment following when there are new features or feature changes to report. </remark> - + <!-- <para> Functionality added or changed: @@ -211,14 +211,22 @@ </para> <itemizedlist> - + <listitem> <para> + For tables created in a MySQL 4.1 installation upgraded to + MySQL 5.0 and up, multiple-table updates could update only the + first matching row. (Bug #16281) + </para> + </listitem> + + <listitem> + <para> <literal>NDB Cluster</literal>: When multiple node restarts were attempted without allowing each restart to complete, the error message returned was <errortext>Array index out of - bounds</errortext> rather than <errortext>Too many crashed - replicas</errortext>. (Bug #18349) + bounds</errortext> rather than <errortext>Too many crashed + replicas</errortext>. (Bug #18349) </para> </listitem> @@ -305,6 +313,20 @@ <listitem> <para> + Complex queries with nested joins could cause a server crash. + (Bug #18279) + </para> + </listitem> + + <listitem> + <para> + The server could deadlock under heavy load while writing to + the binary log. (Bug #18116) + </para> + </listitem> + + <listitem> + <para> A <literal>SELECT ... ORDER BY ...</literal> from a view defined using a function could crash the server. An example of such a view might be <literal>CREATE VIEW AS SELECT SQRT(c1) Modified: trunk/refman-common/news-5.1.xml =================================================================== --- trunk/refman-common/news-5.1.xml 2006-04-05 22:04:43 UTC (rev 1738) +++ trunk/refman-common/news-5.1.xml 2006-04-06 00:35:42 UTC (rev 1739) @@ -31,16 +31,16 @@ <filename>TEMPLATE.news.xml</filename> template in the <filename>refman-common</filename> directory. </remark> - + <section id="news-5-1-10"> - + <title>&title-news-5-1-10;</title> - + <para role="release-level"> This is a new Beta development release, fixing recently discovered bugs. </para> - + <para role="release-non-production"> This Beta release, as any other pre-production release, should not be installed on <emphasis>production</emphasis>-level systems or @@ -48,27 +48,27 @@ data before installing any new version of software. Although MySQL has worked very hard to ensure a high level of quality, protect your data by making a backup as you would for any software beta - release. Please refer to our bug database at + release. Please refer to our bug database at <ulink url="http://bugs.mysql.com/"/> for more details about the individual bugs fixed in this version. </para> - + <para> - This section documents all changes and bug fixes that have been - applied since the last official MySQL release. If you would like to - receive more fine-grained and personalised <emphasis>update - alerts</emphasis> about fixes that are relevant to the version - and features you use, please consider subscribing to - <emphasis>MySQL Network</emphasis> (a commercial MySQL offering). - For more details please see + This section documents all changes and bug fixes that have been + applied since the last official MySQL release. If you would like + to receive more fine-grained and personalised <emphasis>update + alerts</emphasis> about fixes that are relevant to the version and + features you use, please consider subscribing to <emphasis>MySQL + Network</emphasis> (a commercial MySQL offering). For more details + please see <ulink url="http://www.mysql.com/network/advisors.html"/>. </para> - + <remark role="todo"> Uncomment following when there are new features or feature changes to report. </remark> - + <!-- <para> Functionality added or changed: @@ -82,35 +82,35 @@ </itemizedlist> --> - + <para> Bugs fixed: </para> - + <itemizedlist> - + <listitem> <para> <literal>NDB Cluster</literal>: Attempting to create an index using multiple columns on an explicitly partitioned table in a replicated Cluster database could cause the master - <command>mysqld</command> process to crash. (Bug #18284) + <command>mysqld</command> process to crash. (Bug #18284) </para> </listitem> - + <listitem> <para> <literal>NDB Cluster</literal>: Queries using <literal>ORDER - BY <replaceable>pkN</replaceable></literal> failed against a + BY <replaceable>pkN</replaceable></literal> failed against a <literal>LIST</literal>-partitioned Cluster table having a multi-column primary key, where <replaceable>pkN</replaceable> represents one of the columns making up the primary key. (Bug - #18598) + #18598) </para> </listitem> - + </itemizedlist> - + </section> <section id="news-5-1-9"> @@ -121,7 +121,7 @@ This is a new Beta development release, fixing recently discovered bugs. </para> - + <para role="release-non-production"> <emphasis role="bold">NOTE</emphasis>: This Beta release, as any other pre-production release, should not be installed on @@ -133,28 +133,28 @@ refer to our bug database at <ulink url="http://bugs.mysql.com/"/> for more details about the individual bugs fixed in this version. </para> - + <para> - This section documents all changes and bug fixes that have been - applied since the last official MySQL release. If you would like to - receive more fine-grained and personalised <emphasis>update - alerts</emphasis> about fixes that are relevant to the version - and features you use, please consider subscribing to - <emphasis>MySQL Network</emphasis> (a commercial MySQL offering). - For more details please see + This section documents all changes and bug fixes that have been + applied since the last official MySQL release. If you would like + to receive more fine-grained and personalised <emphasis>update + alerts</emphasis> about fixes that are relevant to the version and + features you use, please consider subscribing to <emphasis>MySQL + Network</emphasis> (a commercial MySQL offering). For more details + please see <ulink url="http://www.mysql.com/network/advisors.html"/>. </para> - + <para> Functionality added or changed: </para> <itemizedlist> - + <listitem> <para> For partitioned tables, the output of <literal>SHOW TABLE - STATUS</literal> now shows in the <literal>Engine</literal> + STATUS</literal> now shows in the <literal>Engine</literal> column the name of the storage engine used by all partitions for the table; in the <literal>Create_options</literal> column, the output now shows <literal>partitioned</literal> @@ -164,17 +164,17 @@ #17631) </para> </listitem> - + <listitem> <para> The <literal>NDBCluster</literal> storage engine now supports - <literal>CREATE TABLE</literal> statements of arbitrary length. - (Previously, <literal>CREATE TABLE</literal> statements for MySQL - Cluster tables could contain a maximum of 4096 characters only.) (Bug - #17813) + <literal>CREATE TABLE</literal> statements of arbitrary + length. (Previously, <literal>CREATE TABLE</literal> + statements for MySQL Cluster tables could contain a maximum of + 4096 characters only.) (Bug #17813) </para> </listitem> - + </itemizedlist> <para> @@ -182,21 +182,37 @@ </para> <itemizedlist> - + <listitem> <para> + For tables created in a MySQL 4.1 installation upgraded to + MySQL 5.0 and up, multiple-table updates could update only the + first matching row. (Bug #16281) + </para> + </listitem> + + <listitem> + <para> + Complex queries with nested joins could cause a server crash. + (Bug #18279) + </para> + </listitem> + + <listitem> + <para> A query against a partitioned table using <literal>WHERE - <replaceable>col</replaceable> IS NULL</literal> could - produce incorrect results given the following conditions: + <replaceable>col</replaceable> IS NULL</literal> could produce + incorrect results given the following conditions: </para> - + <itemizedlist> + <listitem> <para> The table had partitions and subpartitions </para> </listitem> - + <listitem> <para> The partitioning function depended on a single column @@ -204,14 +220,15 @@ types </para> </listitem> - + <listitem> <para> The partitioning function was not monotonically increasing </para> </listitem> + </itemizedlist> - + <para> The same issue could cause the server to crash when run in debug mode. (Bug #18659) @@ -227,38 +244,38 @@ sign, and no warning was generated. (Bug #15098) </para> </listitem> - + <listitem> <para> <literal>MEDIUMINT</literal> columns were not handled in the same way as other column types by partition pruning. </para> - + <para> Partition pruning would sometimes use inappropriate columns in preforming queries. </para> - + <para> Both of these issues were rectified as part of the same - bugfix. (Bug #18025) + bugfix. (Bug #18025) </para> </listitem> - + <listitem> <para> Quoted values could not be used for partition option values. (Bug #13520) </para> </listitem> - + <listitem> <para> Delimited identifiers could not be used in defining partitions. (Bug #13433) </para> </listitem> - + <listitem> <para> Building the server using @@ -267,21 +284,21 @@ server. (Bug #18464) </para> </listitem> - + <listitem> <para> Triggers created in one version of the server could not be - dropped after upgrading to a newer version. (Bug #15921) + dropped after upgrading to a newer version. (Bug #15921) </para> - </listitem> - + </listitem> + <listitem> <para> Queries using <literal>WHERE ... IS NULL</literal> returned incorrect results from partitioned tables. (Bug #18070) </para> </listitem> - + <listitem> <para> Partition pruning did not perform correctly with partitions on @@ -293,9 +310,9 @@ <listitem> <para> If <literal>InnoDB</literal> encountered a - <literal>HA_ERR_LOCK_TABLE_FULL</literal> error and - rolled back a transaction, the transaction was still written - to the binary log. (Bug #18283) + <literal>HA_ERR_LOCK_TABLE_FULL</literal> error and rolled + back a transaction, the transaction was still written to the + binary log. (Bug #18283) </para> </listitem> @@ -306,7 +323,7 @@ <section id="news-5-1-8"> <title>&title-news-5-1-8;</title> - + <para> <emphasis role="bold">Note</emphasis>: This was an internal release only, and no binaries were published. @@ -447,7 +464,7 @@ #17754) </para> </listitem> - + <listitem> <para> <emphasis role="bold">Security Enhancement</emphasis>: Checks @@ -457,13 +474,13 @@ on database <literal>myDataBase</literal>. (Bug #17279) </para> </listitem> - + <listitem> <para> The <literal>NDBCluster</literal> storage engine now supports - <literal>INSERT IGNORE</literal> and <literal>REPLACE</literal> - statements. Previously, these statements failed with an error. (Bug - #17431) + <literal>INSERT IGNORE</literal> and + <literal>REPLACE</literal> statements. Previously, these + statements failed with an error. (Bug #17431) </para> </listitem> @@ -474,7 +491,7 @@ beginning of the Unix epoch.) (Bug #16396) </para> </listitem> - + <listitem> <para> Event names are now case-insenstive. That is (for example), @@ -658,17 +675,17 @@ described in <xref linkend="replication-row-based"/>. </para> </listitem> - + <listitem> <para> - A slave server may switch the format - <emphasis>automatically</emphasis> now. - This happens when the server is running in either - <literal>STATEMENT</literal> or <literal>MIXED</literal> format - and encounters a row in the binary log that is written in - <literal>ROW</literal> logging format. In that case, the slave - switches to row-based replication temporarily for that event, and - switches back to the previous format afterwards. + A slave server may switch the format + <emphasis>automatically</emphasis> now. This happens when the + server is running in either <literal>STATEMENT</literal> or + <literal>MIXED</literal> format and encounters a row in the + binary log that is written in <literal>ROW</literal> logging + format. In that case, the slave switches to row-based + replication temporarily for that event, and switches back to + the previous format afterwards. </para> </listitem> @@ -714,14 +731,14 @@ </para> <itemizedlist> - + <listitem> <para> <literal>NDB Cluster</literal>: Attempting to restart a node with dropped events still pending would fail. (Bug #18491) </para> </listitem> - + <listitem> <para> <literal>NDB Cluster</literal>: In asynchronous replication @@ -729,7 +746,7 @@ <command>mysqld</command>. (Bug # 18472) </para> </listitem> - + <listitem> <para> <literal>NDB Cluster</literal>: Two <command>mysqld</command> @@ -737,7 +754,7 @@ condition. (Bug #18472) </para> </listitem> - + <listitem> <para> <literal>NDB Cluster</literal>: Two <command>mysqld</command> @@ -745,70 +762,70 @@ binary log events correctly. (Bug #18395) </para> </listitem> - + <listitem> <para> <literal>NDB Cluster</literal>: When multiple node restarts were attempted without allowing each restart to complete, the error message returned was <errortext>Array index out of - bounds</errortext> rather than <errortext>Too many crashed - replicas</errortext>. (Bug #18349) + bounds</errortext> rather than <errortext>Too many crashed + replicas</errortext>. (Bug #18349) </para> </listitem> - + <listitem> <para> A <literal>SELECT ... ORDER BY ...</literal> from a view defined using a function could crash the server. An example of such a view might be <literal>CREATE VIEW v1 AS SELECT - SQRT(c1) FROM t1</literal>. (Bug #18386) + SQRT(c1) FROM t1</literal>. (Bug #18386) </para> </listitem> - + <listitem> <para> <literal>REPAIR TABLE</literal>, <literal>OPTIMIZE - TABLE</literal>, and <literal>ALTER TABLE</literal> - operations on transactional tables could corrupt triggers - referencing those tables. (Bug #18153) + TABLE</literal>, and <literal>ALTER TABLE</literal> operations + on transactional tables could corrupt triggers referencing + those tables. (Bug #18153) </para> </listitem> - + <listitem> <para> <literal>MyISAM</literal>: Performing a bulk insert on a table referenced by a trigger would crash the table. (Bug #17764) </para> </listitem> - + <listitem> <para> Using <literal>ORDER BY - <replaceable>intvar</replaceable></literal> within a stored + <replaceable>intvar</replaceable></literal> within a stored procedure (where <replaceable>intvar</replaceable> is an integer variable or expression) would crash the server. (Bug #16474) </para> - + <para> - <emphasis role="bold">Note</emphasis>: The use of an integer + <emphasis role="bold">Note</emphasis>: The use of an integer <replaceable>i</replaceable> in an <literal>ORDER BY - <replaceable>i</replaceable></literal> clause for sorting - the result by the + <replaceable>i</replaceable></literal> clause for sorting the + result by the <replaceable>i</replaceable><superscript>th</superscript> column is deprecated (and non-standard). It should <emphasis>not</emphasis> be used in new applications. See <xref linkend="select"/>. </para> </listitem> - + <listitem> <para> A <literal>SELECT</literal> using a function against a nested view would crash the server. (Bug #15683) </para> - </listitem> - + </listitem> + <listitem> <para> <literal>ALTER TABLE ... ADD COLUMN ... AFTER ...</literal> @@ -832,26 +849,26 @@ 2-node Clusters only. (Bug #18385) </para> </listitem> - + <listitem> <para> <literal>NDB Cluster</literal>: In event of a node failure during a rollback, a <quote>false</quote> lock could be established on the backup for that node, which lock could not - be removed without restarting the node. (Bug #18352) + be removed without restarting the node. (Bug #18352) </para> </listitem> - + <listitem> <para> <literal>NDB Cluster</literal>: The cluster created a crashed replica of a table having an ordered index — or when logging was not enabled, of a table having a table or unique index — leading to a crash of the cluster following 8 - successibe restarts. (Bug #18298) + successibe restarts. (Bug #18298) </para> </listitem> - + <listitem> <para> <literal>NDB Cluster</literal>: When replacing a failed master @@ -860,30 +877,30 @@ of data to write to the cluster log. (Bug #18118) </para> </listitem> - + <listitem> <para> - <literal>NDB Cluster</literal>: Restarting nodes were allowed to start - and join the cluster too early. (Bug #16772) + <literal>NDB Cluster</literal>: Restarting nodes were allowed + to start and join the cluster too early. (Bug #16772) </para> </listitem> - + <listitem> <para> - <literal>NDB Cluster</literal>: Issuing a <literal>DROP LOGFILE - GROUP</literal> statement would cause <command>ndbd</command> - processes to crash if MySQL had been compiled with - <command>gcc4</command>. (Bug #18295) + <literal>NDB Cluster</literal>: Issuing a <literal>DROP + LOGFILE GROUP</literal> statement would cause + <command>ndbd</command> processes to crash if MySQL had been + compiled with <command>gcc4</command>. (Bug #18295) </para> </listitem> - + <listitem> <para> - Using triggers with partitioned <literal>InnoDB</literal> tables led - to incorrect results. (Bug #17744) + Using triggers with partitioned <literal>InnoDB</literal> + tables led to incorrect results. (Bug #17744) </para> </listitem> - + <listitem> <para> Calling <literal>CREATE TABLE</literal> or <literal>ALTER
| Thread | ||
|---|---|---|
| • svn commit - mysqldoc@docsrva: r1739 - in trunk: . refman-common | paul | 6 Apr |
© 1995-2008 MySQL AB, 2008-2009 Sun Microsystems, Inc.
Page generated in 0.694 sec. using MySQL 5.1.14-beta-log