Author: jstephens
Date: 2007-02-01 04:57:00 +0100 (Thu, 01 Feb 2007)
New Revision: 4726
Log:
Updated versioning/version string info for Telco releases.
Added copy of 5.1.15-main changelog to Telco changelog.
Modified:
branches/telcos/refman-5.1/introduction.xml
branches/telcos/refman-5.1/news-5.1.xml
branches/telcos/refman-5.1/renamed-nodes.txt
Modified: branches/telcos/refman-5.1/introduction.xml
===================================================================
--- branches/telcos/refman-5.1/introduction.xml 2007-02-01 02:08:49 UTC (rev 4725)
+++ branches/telcos/refman-5.1/introduction.xml 2007-02-01 03:57:00 UTC (rev 4726)
Changed blocks: 1, Lines Added: 14, Lines Deleted: 11; 2283 bytes
@@ -178,17 +178,20 @@
versions. If you are not using MySQL ¤t-series;, please
refer to the version of the Manual appropriate to the version
which you are using, which can be found on the MySQL web site at
- <ulink url="&base-url-refman;"/>. MySQL ¤t-series; branched
- from the main MySQL development tree beginning with MySQL 5.1.14,
- and are distinguished from the mainline versions by the addition
- of
- NDB-<replaceable>x</replaceable>.<replaceable>y</replaceable>.<replaceable>z</replaceable>
- to the version string. The first release of MySQL ¤t-series;
- was MySQL 5.1.14/NDB-6.1.0-beta. <emphasis>All</emphasis> minor
- versions of MySQL ¤t-series; contain <quote>5.1.14</quote>
- in the version string; the Telco Edition releases are identified
- by this NDB release number
- (NDB-<replaceable>x</replaceable>.<replaceable>y</replaceable>.<replaceable>z</replaceable>).
+ <ulink url="&base-url-refman;"/>. MySQL ¤t-series; branch
+ from the main MySQL 5.1 development tree, and are distinguished
+ from the mainline versions by a two-part version string of the
+ form <literal>MySQL
+ <replaceable>i</replaceable>.<replaceable>j</replaceable>.<replaceable>k</replaceable>/NDB-<replaceable>x</replaceable>.<replaceable>y</replaceable>.<replaceable>z</replaceable></literal>,
+ where the portion <emphasis>preceding</emphasis> the slash
+ character indicates the MySQL mainline version on which the
+ release is based, and may be the same for different MySQL
+ ¤t-series; releases. The portion of the version string
+ <emphasis>following</emphasis> the slash indicates the
+ <literal>NDB</literal> storage engine version; this is different
+ for each ¤t-series; release. The first release of MySQL
+ ¤t-series; was MySQL 5.1.14/NDB-6.1.0-beta; the second
+ release is MySQL 5.1.15/NDB-6.1.1-beta.
</para>
<para>
Modified: branches/telcos/refman-5.1/news-5.1.xml
===================================================================
--- branches/telcos/refman-5.1/news-5.1.xml 2007-02-01 02:08:49 UTC (rev 4725)
+++ branches/telcos/refman-5.1/news-5.1.xml 2007-02-01 03:57:00 UTC (rev 4726)
Changed blocks: 4, Lines Added: 1353, Lines Deleted: 5; 47708 bytes
@@ -13,7 +13,9 @@
]>
<section id="news-5-1-x">
- <title>Changes in release 5.1.<replaceable>X</replaceable> (Telco Edition)</title>
+ <title>Changes in release
+ 5.1.<replaceable>X</replaceable>/NDB-6.1.<replaceable>X</replaceable>
+ (Telco Edition)</title>
<indexterm>
<primary>changes</primary>
@@ -36,9 +38,9 @@
<filename>refman-common</filename> directory.
</remark>
- <section id="news-5-1-14-ndb-6-1-1">
+ <section id="news-5-1-15-ndb-6-1-1">
- <title>Changes in release MySQL 5.1.14/NDB-6.1.1-beta (Not yet released)</title>
+ <title>Changes in release MySQL 5.1.15/NDB-6.1.1-beta (Not yet released)</title>
<para role="release-level">
This is a new Beta development release, fixing recently discovered
@@ -71,8 +73,11 @@
<para>
This section documents all changes and bug fixes that have been
applied in the second MySQL Cluster Telco Edition Beta release
- — also known as MySQL Cluster 5.1.14/NDB-6.1.1 — since
- the release of MySQL Cluster 5.1.14/NDB-6.1.0.
+ — also known as MySQL Cluster 5.1.15/NDB-6.1.1 — since
+ the release of MySQL Cluster 5.1.14/NDB-6.1.0. This version also
+ incorporates all bugfixes and feature changes which were added in
+ the mainline 5.1.15 release; information about these can be found
+ in <xref linkend="news-5-1-15"/>.
</para>
<para>
@@ -140,7 +145,1350 @@
</itemizedlist>
</section>
+
+ <section id="news-5-1-15">
+ <title>Changes in release 5.1.15 (Not separately released for MySQL
+ ¤t-series;)</title>
+
+ <para>
+ This section documents all changes and bug fixes that were applied
+ in MySQL 5.1.15 and subsequently incorporated into MySQL
+ 5.1.15/NDB-6.1.1.
+ </para>
+
+ <para>
+ Functionality added or changed:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ <emphasis role="bold">Incompatible change</emphasis>: The
+ following conditions apply to enabling the
+ <literal>read_only</literal> system variable:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ If you attempt to enable <literal>read_only</literal>
+ while you have any explicit locks (acquired with
+ <literal>LOCK TABLES</literal> or have a pending
+ transaction, an error will occur.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ If other clients hold explicit table locks or have pending
+ transactions, the attempt to enable
+ <literal>read_only</literal> blocks until the locks are
+ released and the transactions end. While the attempt to
+ enable <literal>read_only</literal> is pending, requests
+ by other clients for table locks or to begin transactions
+ also block until <literal>read_only</literal> has been
+ set.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>read_only</literal> can be enabled while you hold
+ a global read lock (acquired with <literal>FLUSH TABLES
+ WITH READ LOCK</literal>) because that does not involve
+ table locks.
+ </para>
+
+<!--
+This means that the following sequence of
+ statements can be used to place a server in read-only
+ state prior to performing a backup:
+ </para>
+
+<programlisting>
+FLUSH TABLES WITH READ LOCK;
+SET GLOBAL read_only = ON;
+UNLOCK TABLES;
+</programlisting>
+-->
+ </listitem>
+
+ </itemizedlist>
+
+ <para>
+ Previously, the attempt to enable <literal>read_only</literal>
+ would return immediately even if explicit locks or
+ transactions were pending, so some data changes could occur
+ for statements executing in the server at the same time. (Bug
+ #11733, Bug #22009)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <emphasis role="bold">Incompatible change</emphasis>:
+ Previously, the <literal>DATE_FORMAT()</literal> function
+ returned a binary string. Now it returns a string with a
+ character set and collation given by
+ <literal>character_set_connection</literal> and
+ <literal>collation_connection</literal> so that it can return
+ month and weekday names containing non-ASCII characters. (Bug
+ #22646)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The <option>--skip-thread-priority</option> option now is
+ enabled by default for binary Mac OS X distributions. Use of
+ thread priorities degrades performance on Mac OS X. (Bug
+ #18526)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Added the <option>--disable-grant-options</option> option to
+ <command>configure</command>. If <command>configure</command>
+ is run with this option, the <option>--bootstrap</option>,
+ <option>--skip-grant-tables</option>, and
+ <option>--init-file</option> options for
+ <command>mysqld</command> are disabled and cannot be used. For
+ Windows, the <command>configure.js</command> script recognizes
+ the <literal>DISABLE_GRANT_OPTIONS</literal> flag, which has
+ the same effect.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Partitioning of tables using the <literal>FEDERATED</literal>
+ storage engine is no longer permitted. Attempting to create
+ such a table or to modify an existing table so that is uses
+ both partitioning and <literal>FEDERATED</literal> now fails
+ with an error. (Bug #22451)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ In MySQL ¤t-series;, <literal>InnoDB</literal> rolls
+ back only the last statement on a transaction timeout. A new
+ option, <option>--innodb_rollback_on_timeout</option>, causes
+ <literal>InnoDB</literal> to abort and roll back the entire
+ transaction if a transaction timeout occurs (the same behavior
+ as in MySQL 4.1). (Bug #24200)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The <literal>Com_create_user</literal> status variable was
+ added (for counting <literal>CREATE USER</literal>
+ statements). (Bug #22958)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The <option>--memlock</option> option relies on system calls
+ that are unreliable on some operating systems. If a crash
+ occurs, the server now checks whether
+ <option>--memlock</option> was specified and if so issues some
+ information about possible workarounds. (Bug #22860)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The default value of the <literal>max_connections</literal>
+ variable has been increased to 151 in order that Websites
+ running on Apache and using MySQL will not have more processes
+ trying to access MySQL than the default number of connections
+ available.
+ </para>
+
+ <para>
+ (The maximum number of Apache processes is determined by the
+ Apache <literal>MaxClient</literal>, which defaults to 256,
+ but is usually set to 150 in the
+ <filename>httpd.conf</filename> commonly distributed with
+ Apache. For more information about
+ <literal>MaxClient</literal>, see
+ <ulink url="http://httpd.apache.org/docs/2.2/mod/mpm_common.html#maxclients"/>.)
+ </para>
+
+ <para>
+ (Bug #23883)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The bundled yaSSL library was upgraded to version 1.5.0.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Calling a non-deterministic stored routine when using
+ statement-based replication now throws an error. Formerly,
+ defining such a stored routine would cause an error to be
+ thrown. (Bug #16456)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The (undocumented) <literal>UNIQUE_USERS()</literal> and and
+ <literal>GROUP_UNIQUE_USERS()</literal> functions were
+ removed. (Bug #22687)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: The
+ <literal>LockPagesInMainMemory</literal> configuration
+ parameter has changed its type and possible values. For more
+ information, see
+ <literal><link linkend="mysql-cluster-param-ndbd-definition-lockpagesinmainmemory">LockPagesInMainMemory</link></literal>.
+ (Bug #25686)
+ </para>
+
+ <para>
+ <emphasis role="bold">Important</emphasis>: The values
+ <literal>true</literal> and <literal>false</literal> are no
+ longer accepted for this parameter. If you were using this
+ parameter and had it set to <literal>false</literal> in a
+ previous release, you must change it to <literal>0</literal>.
+ If you had this parameter set to <literal>true</literal>, you
+ should instead use <literal>1</literal> to obtain the same
+ behavior as previously, or <literal>2</literal> to take
+ advantage of new functionality introduced with this release
+ described in the section cited above.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ <para>
+ Bugs fixed:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ If there was insufficient memory available to
+ <command>mysqld</command>, this could sometimes cause the
+ server to hang during startup. (Bug #24751)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Using row-based replication to replicate to a table having at
+ least one extra <literal>BIT</literal> column with a default
+ value on the slave as compared to the master could cause the
+ slave to fail. (Bug #24490)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Optimizations that are legal only for subqueries without
+ tables and <literal>WHERE</literal> conditions were applied
+ for any subquery without tables. (Bug #24670)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A query using <literal>WHERE
+ <replaceable>unsigned_column</replaceable> NOT IN
+ ('<replaceable>negative_value</replaceable>')</literal>
+ could cause the server to crash. (Bug #24261)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A <literal>FETCH</literal> statement using a cursor on a table
+ which was not in the table cache could sometimes cause the
+ server to crash. (Bug #24117)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>CREATE TABLE ... SELECT</literal> statements were not
+ rolled back correctly. As part of the fix, such a statement
+ now causes an implicit commit before and after it is executed.
+ However, it does not cause a commit when used to create a
+ temporary table. (Bug #22864)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ SSL connections could hang at connection shutdown. (Bug
+ #24148)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The <literal>STDDEV()</literal> function returned a positive
+ value for data sets consisting of a single value. (Bug #22555)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <command>mysqltest</command> incorrectly tried to retrieve
+ result sets for some queries where no result set was
+ available. (Bug #19410)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <command>mysqltest</command> crashed with a stack overflow.
+ (Bug #24498)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The server was built even when <command>configure</command>
+ was run with the <option>--without-server</option> option.
+ (Bug #23973)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <filename>mysqld_error.h</filename> was not installed when
+ only the client libraries were built. (Bug #21265)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <command>mysql_install_db</command> did not create the
+ <literal>mysql.plugin</literal> table if strict SQL mode was
+ enabled. (Bug #24270)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The row count for <literal>MyISAM</literal> tables was not
+ updated properly, causing <literal>SHOW TABLE STATUS</literal>
+ to report incorrect values. (Bug #23526)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Using a view in combination with a <literal>USING</literal>
+ clause caused column aliases to be ignored. (Bug #25106)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Using <literal>ALTER TABLE</literal> to convert a
+ <literal>CSV</literal> table containing
+ <literal>NULL</literal> values to <literal>MyISAM</literal>
+ resulted in warnings. (Bug #21328)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A view was not handled correctly if the
+ <literal>SELECT</literal> part contained
+ ‘<literal>\Z</literal>’. (Bug #24293)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Inserting a row into a table without specifying a value for a
+ <literal>BINARY(<replaceable>N</replaceable>) NOT
+ NULL</literal> column caused the column to be set to spaces,
+ not zeroes. (Bug #14171)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ An assertion failed incorrectly for prepared statements that
+ contained a single-row non-correlated subquery that was used
+ as an argument of the IS NULL predicate. (Bug #25027)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A table created with the <literal>ROW_FORMAT = FIXED</literal>
+ table option loses the option if an index is added or dropped
+ with <literal>CREATE INDEX</literal> or <literal>DROP
+ INDEX</literal>. (Bug #23404)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Dropping a user-defined function sometimes did not remove the
+ UDF entry from the <literal>mysql.proc</literal> table. (Bug
+ #15439)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The <command>BUILD/check-cpu</command> script did not
+ recognize Celeron processors. (Bug #20061)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Some problems uncovered by Valgrind were fixed. (Bug #25396)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <command>mysql_fix_privilege_tables</command> did not handle a
+ password containing embedded space or apostrophe characters.
+ (Bug #17700)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Foreign key identifiers for <literal>InnoDB</literal> tables
+ could not contain certain characters. (Bug #24299)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ On Windows, the <literal>SLEEP()</literal> function could
+ sleep too long, especially after a change to the system clock.
+ (Bug #14094, Bug #17635, Bug #24686)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ In the <literal>INFORMATION_SCHEMA.KEY_COLUMN_USAGE</literal>
+ table, the value displayed for the
+ <literal>REFERENCED_TABLE_NAME</literal> column was the table
+ name as encoded for disk storage, not the actual table name.
+ (Bug #25026)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Changing the value of <literal>MI_KEY_BLOCK_LENGTH</literal>
+ in <filename>myisam.h</filename> and recompiling MySQL
+ resulted in a <command>myisamchk</command> that saw existing
+ <literal>MyISAM</literal> tables as corrupt. (Bug #22119)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A stored routine containing semicolon in its body could not be
+ reloaded from a dump of a binary log. (Bug #20396)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ For <literal>SET</literal>, <literal>SELECT</literal>, and
+ <literal>DO</literal> statements that invoked a stored
+ function from a database other than the default database, the
+ function invocation could fail to be replicated. (Bug #19725)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ For <literal>ENUM</literal> columns defined such that
+ enumeration values contained commas, the commas were mapped to
+ <literal>0xff</literal>. (Bug #24660)
+ </para>
+
+ <para>
+ <emphasis role="bold">Upgrade note</emphasis>: The fix for
+ this problem affects tables containing <literal>ENUM</literal>
+ columns that actually do have <literal>0xff</literal> in
+ enumeration values. Such tables should be dumped using
+ <command>mysqldump</command> with the current server before
+ upgrading to MySQL 5.1.15 or higher and reloading the tables.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>SET lc_time_names =
+ <replaceable>value</replaceable></literal> allowed only exact
+ literal values, not expression values. (Bug #22647)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Changes to the <literal>lc_time_names</literal> system
+ variable were not replicated. (Bug #22645)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>SELECT ... FOR UPDATE</literal>, <literal>SELECT ...
+ LOCK IN SHARE MODE</literal>, <literal>DELETE</literal>, and
+ <literal>UPDATE</literal> statements executed using a full
+ table scan were not releasing locks on rows that did not
+ satisfy the <literal>WHERE</literal> condition. (Bug #20390)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A stored procedure, executed from a connection using a binary
+ character set, and which wrote multibyte data, would write
+ incorrectly escaped entries to the binary log. This caused
+ syntax errors, and caused replication to fail. (Bug #23619,
+ Bug #24492)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <command>mysqldump --order-by-primary</command> failed if the
+ primary key name was an identifier that required quoting. (Bug
+ #13926)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Re-execution of <literal>CREATE DATABASE</literal>,
+ <literal>CREATE TABLE</literal>, and <literal>ALTER
+ TABLE</literal> statements in stored routines or as prepared
+ statements caused incorrect results. (Bug #22060)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The internal functions for table preparation, creation, and
+ alteration were not re-execution friendly, causing problems in
+ code that: repeatedly altered a table; repeatedly created and
+ dropped a table; opened and closed a cursor on a table,
+ altered the table, and then reopened the cursor. (Bug #4968,
+ Bug #6895, Bug #19182, Bug #19733)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A workaround was implemented to avoid a race condition in the
+ NPTL <literal>pthread_exit()</literal> implementation. (Bug
+ #24507)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The Instance Manager <literal>DROP INSTANCE</literal> command
+ did not work. (Bug #23476)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The Instance Manager <literal>STOP INSTANCE</literal> command
+ took too much time and caused Instance Manager to be
+ unresponsive. (Bug #23215)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The Instance Manager <literal>STOP INSTANCE</literal> command
+ could not be applied to instances in the
+ <literal>Crashed</literal>, <literal>Failed</literal>, or
+ <literal>Abandoned</literal> state. (Bug #22306)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Instance Manager could crash during shutdown. (Bug #19044)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A deadlock could occur, with the server hanging on
+ <literal>Closing tables</literal>, with a sufficient number of
+ concurrent <literal>INSERT DELAYED</literal>, <literal>FLUSH
+ TABLES</literal>, and <literal>ALTER TABLE</literal>
+ operations. (Bug #23312)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A user-defined variable could be assigned an incorrect value
+ if a temporary table was employed in obtaining the result of
+ the query used to determine its value. (Bug #16861)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The optimizer removes expressions from <literal>GROUP
+ BY</literal> and <literal>DISTINCT</literal> clauses if they
+ happen to participate in
+ <literal><replaceable>expression</replaceable> =
+ <replaceable>constant</replaceable></literal> predicates of
+ the <literal>WHERE</literal> clause, the idea being that, if
+ the expression is equal to a constant, then it cannot take on
+ multiple values. However, for predicates where the expression
+ and the constant item are of different result types (for
+ example, when a string column is compared to 0), this is not
+ valid, and can lead to invalid results in such cases. The
+ optimizer now performs an additional check of the result types
+ of the expression and the constant; if their types differ,
+ then the expression is not removed from the <literal>GROUP
+ BY</literal> list. (Bug #15881)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Referencing an ambiguous column alias in an expression in the
+ <literal>ORDER BY</literal> clause of a query caused the
+ server to crash. (Bug #25427)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Some <literal>CASE</literal> statements inside stored routines
+ could lead to excessive resource usage or a crash of the
+ server. (Bug #24854, Bug #19194)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Some joins in which one of the joined tables was a view could
+ return erroneous results or crash the server. (Bug #24345)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>OPTIMIZE TABLE</literal> tried to sort R-tree indexes
+ such as spatial indexes, although this is not possible (see
+ <xref linkend="optimize-table"/>). (Bug #23578)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ User-defined variables could consume excess memory, leading to
+ a crash caused by the exhaustion of resources available to the
+ <literal>MEMORY</literal> storage engine, due to the fact that
+ this engine is used by MySQL for variable storage and
+ intermediate results of <literal>GROUP BY</literal> queries.
+ Where <literal>SET</literal> had been used, such a condition
+ could instead give rise to the misleading error message
+ <errortext>You may only use constant expressions with
+ SET</errortext>, rather than <errortext>Out of memory (Needed
+ NNNNNN bytes)</errortext>. (Bug #23443)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>InnoDB</literal>: During a restart of the MySQL
+ Server that followed the creation of a temporary table using
+ the <literal>InnoDB</literal> storage engine, MySQL failed to
+ clean up in such a way that <literal>InnoDB</literal> still
+ attempted to find the files associated with such tables. (Bug
+ #20867)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Under some circumstances, a <literal>REORGANIZE
+ PARTITION</literal> statement could crash
+ <command>mysqld</command>. (Bug #24502)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A multi-table <literal>DELETE QUICK</literal> could sometimes
+ cause one of the affected tables to become corrupted. (Bug
+ #25048)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A compressed <literal>MyISAM</literal> table that became
+ corrupted could crash <command>myisamchk</command> and
+ possibly the MySQL Server. (Bug #23139)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Using <literal>INSTALL PLUGIN</literal> followed by a restart
+ of the server caused an error due to memory not being properly
+ initialized. (Bug #22694)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A crash of the MySQL Server could occur when unpacking a
+ <literal>BLOB</literal> column from a row in a corrupted
+ MyISAM table. This could happen when trying to repair a table
+ using either <literal>REPAIR TABLE</literal> or
+ <command>myisamchk</command>; it could also happen when trying
+ to access such a <quote>broken</quote> row using statements
+ like <literal>SELECT</literal> if the table was not marked as
+ crashed. (Bug #22053)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The <literal>FEDERATED</literal> storage engine did not
+ support the <literal>euckr</literal> character set. (Bug
+ #21556)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The <literal>FEDERATED</literal> storage engine did not
+ support the <literal>utf8</literal> character set. (Bug
+ #17044)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <command>mysql_upgrade</command> failed if the
+ <literal>--password</literal> (or <option>-p</option>) option
+ was given. (Bug #24896)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ For a nonexistent table, <literal>DROP TEMPORARY
+ TABLE</literal> failed with an incorrect error message if
+ <literal>read_only</literal> was enabled. (Bug #22077)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The code for generating <literal>USE</literal> statements for
+ binary logging of <literal>CREATE PROCEDURE</literal>
+ statements resulted in confusing output from
+ <command>mysqlbinlog</command> for <literal>DROP
+ PROCEDURE</literal> statements. (Bug #22043)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The <literal>REPEAT()</literal> function could return
+ <literal>NULL</literal> when passed a column for the count
+ argument. (Bug #24947)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Accuracy was improved for comparisons between
+ <literal>DECIMAL</literal> columns and numbers represented as
+ strings. (Bug #23260)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>InnoDB</literal> crashed while performing XA recovery
+ of prepared transactions. (Bug #21468)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>ROW_COUNT()</literal> did not work properly as an
+ argument to a stored procedure. (Bug #23760)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ It was possible to use <literal>DATETIME</literal> values
+ whose year, month, and day parts were all zeroes but whose
+ hour, minute, and second parts contained nonzero values, an
+ example of such an illegal <literal>DATETIME</literal> being
+ <literal>'0000-00-00 11:23:45'</literal>. (Bug #21789)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ It was possible to set the backslash character (<quote>
+ <literal>\</literal> </quote>) as the delimiter character
+ using <literal>DELIMITER</literal>, but not actually possible
+ to use it as the delimiter. (Bug #21412)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>ALTER ENABLE KEYS</literal> or <literal>ALTER TABLE
+ DISABLE KEYS</literal> combined with another <literal>ALTER
+ TABLE</literal> option other than <literal>RENAME TO</literal>
+ did nothing. In addition, if ALTER TABLE was used on a table
+ having disabled keys, the keys of the resulting table were
+ enabled. (Bug #24395)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ An <literal>ALTER TABLE</literal> statement that used a
+ <literal>RENAME</literal> clause in combination with a
+ <literal>MODIFY</literal> or <literal>CHANGE</literal> that
+ did not actually change the table (for example, when it
+ changed a column's type from <literal>INT</literal> to
+ <literal>INT</literal>). The behavior caused by this bug
+ differed according to whether or not the storage engine used
+ by the table was transactional or non-transactional. For
+ transactional tables (such as those using the
+ <literal>InnoDB</literal> storage engine), the statement
+ simply failed; for non-transactional tables (such as those
+ using the <literal>MyISAM</literal> storage engine), the
+ <literal>ALTER TABLE</literal> statement succeeding renaming
+ the table, but subsequent <literal>SELECT</literal> statements
+ against the renamed table would fail. (Bug #22369)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Queries of the form <literal>SELECT ... WHERE
+ <replaceable>string</replaceable> = ANY(...)</literal> failed
+ when the server used a single-byte character set and the
+ client used a multi-byte character set. (Bug #20835)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A partitioned table that used the <literal>DATA
+ DIRECTORY</literal> option, where the data directory was the
+ same as the directory in which the table definition file
+ resided, became corrupted following <literal>ALTER TABLE
+ ENGINE=ARCHIVE</literal>. This was actually due to an issue
+ with the <literal>ARCHIVE</literal> storage engine, and not
+ with partitioned tables in general. (Bug #22634)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal> (Cluster APIs): Deletion of an
+ <literal>Ndb_cluster_connection</literal> object took a very
+ long time. (Bug #25487)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal> (Replication): Certain errors
+ in replication setups could lead to subsequent node failures.
+ (Bug #25755)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal> (Replication): Connecting a
+ <command>mysqld</command> to a cluster where not all nodes
+ were running, starting the remaining cluster nodes, and then
+ disconnecting from the cluster caused the
+ <command>mysqld</command> process to crash. (Bug #25387)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal> (Replication): Connecting an
+ API node to the cluster during a node restart while performing
+ database operations could cause the restarting node to fail.
+ (Bug #25329)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal> (Disk Data): Following 3 or
+ more missed local checkpoints by a cluster node, a restart of
+ the node caused incorrect undo information to be used for Disk
+ Data tables. (Bug #25636)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal> (Disk Data): Issuing a
+ <literal>TRUNCATE</literal> statement on a Disk Data table
+ caused the table to become an in-memory table. (Bug #25296)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal> (Disk Data): Changing a column
+ specification on a Disk Data table caused the table to become
+ an in-memory table. (Bug #24667)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: It was not possible to create
+ an <literal>NDB</literal> table with a key on two
+ <literal>VARCHAR</literal> columns where both columns had a
+ storage length in excess of 256. (Bug #25746)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: Hosts in clusters with a large
+ number of nodes could experience excessive CPU usage while
+ obtaining configuration data. (Bug #25711)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: In some circumstances,
+ shutting down the cluster could cause connected
+ <command>mysqld</command> processes to crash. (Bug #25668)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: Non-32-bit, non-aligned
+ columns were not handled correctly in explicitly partitioned
+ <literal>NDB</literal> tables. (Bug #25587)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: Some aggregate queries such as
+ <literal>SELECT COUNT(*)</literal> performed a table scan on
+ <literal>NDB</literal> tables rather than checking table
+ statistics, causing such queries to perform much more slowly
+ in MySQL Cluster 5.1 than in 5.0. (Bug #25567)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: Memory allocations for
+ <literal>TEXT</literal> columns were calculated incorrectly,
+ resulting in space being wasted and other issues. (Bug #25562)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: The failure of a master node
+ during a node restart could lead to a resource leak, causing
+ later node failures. (Bug #25554)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: The failure of a node during a
+ local checkpoint could lead to other node failures. (Bug
+ #25468)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: A node shutdown occurred if
+ the master failed during a commit. (Bug #25364)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: Creating a non-unique index
+ with the <literal>USING HASH</literal> clause silently created
+ an ordered index instead of issuing a warning. (Bug #24820)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: The management server did not
+ handle logging of node shutdown events correctly in certain
+ cases. (Bug #22013)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: A potential memory leak in the
+ <literal>NDB</literal> storage engine's handling of file
+ operations was uncovered. (Bug #21858)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: When stopping and restarting
+ multiple data nodes, the last node to be restarted would
+ sometimes hang in Phase 100. (Bug #19645)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal> (NDB API): Invoking the
+ <literal>NdbTransaction::execute()</literal> method using
+ execution type <literal>Commit</literal> and abort option
+ <literal>AO_IgnoreError</literal> could lead to a crash of the
+ transaction coordinator (<literal>DBTC</literal>). (Bug
+ #25090)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal> (NDB API): A unique index
+ lookup on a non-existent tuple could lead to a data node
+ timeout (error 4012). (Bug #25059)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal> (NDB API): Due to an error in
+ the computation of table fragment arrays, some transactions
+ might not be executed from the correct starting point. (Bug
+ #24914)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal> (Replication): Following a
+ restart of the master cluster, the latest GCI was set to 0
+ upon reconnection to the slave. (Bug #21806)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal> (Disk Data): A
+ <literal>MEDIUMTEXT</literal> column of a Disk Data table was
+ stored in memory rather than on disk, even if the column was
+ not indexed. (Bug #25001)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal> (Disk Data): Performing a node
+ restart with a newly dropped Disk Data table could lead to
+ failure of the node during the restart. (Bug #24917)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal> (Disk Data): When restoring
+ from backup a cluster containing any Disk Data tables with
+ hidden primary keys, a node failure resulted which could lead
+ to a crash of the cluster. (Bug #24166)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal> (Disk Data): Repeated
+ <literal>CREATE</literal>, <literal>DROP</literal>, or
+ <literal>TRUNCATE</literal> in various combinations with
+ system restarts between these operations could lead to the
+ eventual failure of a system restart. (Bug #21948)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal> (Disk Data): Extents that
+ should have been available for re-use following a DROP TABLE
+ operation were not actually made available again until after
+ the cluster performed a local checkpoint. (Bug #17605)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: Under certain rare
+ circumstances, local checkpoints were not performed properly,
+ leading to an inability to restart one or more data nodes.
+ (Bug #24664)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal> (NDB API): When using the
+ <literal>NdbTransaction::execute()</literal> method, a very
+ long timeout (greater than 5 minutes) could result if the last
+ data node being polled was disconnected from the cluster. (Bug
+ #24949)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: When a data node was shut down
+ using the management client <literal>STOP</literal> command, a
+ connection event (<literal>NDB_LE_Connected</literal>) was
+ logged instead of a disconnection event
+ (<literal>NDB_LE_Disconnected</literal>). (Bug #22773)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: <literal>SELECT</literal>
+ statements with a <literal>BLOB</literal> or
+ <literal>TEXT</literal> column in the selected column list and
+ a <literal>WHERE</literal> condition including a primary key
+ lookup on a <literal>VARCHAR</literal> primary key produced
+ empty result sets. (Bug #19956)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: <command>ndb_config</command>
+ failed when trying to use 2 management servers and node IDs.
+ (Bug #23887)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>STR_TO_DATE()</literal> returned
+ <literal>NULL</literal> if the format string contained a space
+ following a non-format character. (Bug #22029)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ yaSSL crashed on pre-Pentium Intel CPUs. (Bug #21765)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Selecting into variables sometimes returned incorrect wrong
+ results. (Bug #20836)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Inserting <literal>DEFAULT</literal> into a column with no
+ default value could result in garbage in the column. Now the
+ same result occurs as when inserting <literal>NULL</literal>
+ into a <literal>NOT NULL</literal> column. (Bug #20691)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <filename>mysql_fix_privilege_tables.sql</filename> altered
+ the <literal>table_privs.table_priv</literal> column to
+ contain too few privileges, causing loss of the
+ <literal>CREATE VIEW</literal> and <literal>SHOW
+ VIEW</literal> privileges. (Bug #20589)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A server crash occurred when using <literal>LOAD
+ DATA</literal> to load a table containing a <literal>NOT
+ NULL</literal> spatial column, when the statement did not load
+ the spatial column. Now a <literal>NULL supplied to NOT NULL
+ column</literal> error occurs. (Bug #22372)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Unsigned <literal>BIGINT</literal> values treated as signed
+ values by the <literal>MOD()</literal> function. (Bug #19955)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Compiling PHP 5.1 with the MySQL static libraries failed on
+ some versions of Linux. (Bug #19817)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The <literal>DELIMITER</literal> statement did not work
+ correctly when used in an SQL file run using the
+ <literal>SOURCE</literal> statement. (Bug #19799)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>VARBINARY</literal> column values inserted on a MySQL
+ 4.1 server had trailing zeroes following upgrade to MySQL 5.0
+ or later. (Bug #19371)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Subqueries of the form <literal>NULL IN (SELECT ...)</literal>
+ returned invalid results. (Bug #8804, Bug #23485)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The <option>--extern</option> option for
+ <command>mysql-test-run.pl</command> did not function
+ correctly. (Bug #24354)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>ALTER TABLE</literal> statements that performed both
+ <literal>RENAME TO</literal> and <literal>{ENABLE|DISABLE}
+ KEYS</literal> operations caused a server crash. (Bug #24089)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The MySQL 5.1.12 binaries for Windows were missing the
+ <literal>FEDERATED</literal>, <literal>EXAMPLE</literal>, and
+ <literal>BLACKHOLE</literal> storage engines. (Bug #23900)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <command>myisampack</command> wrote to unallocated memory,
+ causing a crash. (Bug #17951)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Some small double precision numbers (such as
+ <literal>1.00000001e-300</literal>) that should have been
+ accepted were truncated to zero. (Bug #22129)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The <command>mysql.server</command> script used the
+ <command>source</command> command, which is less portable than
+ the <command>.</command> command; it now uses
+ <command>.</command> instead. (Bug #24294)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>DATE_ADD()</literal> requires complete dates with no
+ <quote>zero</quote> parts, but sometimes did not return
+ <literal>NULL</literal> when given such a date. (Bug #22229)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Using <literal>FLUSH TABLES</literal> in one connection while
+ another connection is using <literal>HANDLER</literal>
+ statements caused a server crash. (Bug #21587)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>FLUSH LOGS</literal> or <command>mysqladmin
+ flush-logs</command> caused a server crash if the binary log
+ was not open. (Bug #17733)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ On HP-UX, <command>mysqltest</command> (non-thread-safe)
+ crashed due to being linked against a thread-safe
+ <literal>libmysys</literal> library. (Bug #23984)
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ </section>
+
<section id="news-5-1-14-ndb-6-1-0">
<title>Changes in release MySQL 5.1.14/NDB-6.1.0-beta (20 December 2006)</title>
Modified: branches/telcos/refman-5.1/renamed-nodes.txt
===================================================================
--- branches/telcos/refman-5.1/renamed-nodes.txt 2007-02-01 02:08:49 UTC (rev 4725)
+++ branches/telcos/refman-5.1/renamed-nodes.txt 2007-02-01 03:57:00 UTC (rev 4726)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 0; 564 bytes
@@ -366,3 +366,4 @@
se-falcon-principles-recordslot http://dev.mysql.com/doc/falcon/en/se-falcon-principles-recordslot.html
se-falcon-limits http://dev.mysql.com/doc/falcon/en/se-falcon-limits.html
+news-5-1-14-ndb-6-1-1 news-5-1-15-ndb-6-1-1
\ No newline at end of file
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r4726 - branches/telcos/refman-5.1 | jon | 1 Feb |
