This is a Monthly Rapid Update release of the MySQL Enterprise Server 5.0.
This section documents all changes and bugfixes that have been applied since the last MySQL Enterprise Server release (5.0.54). If you would like to receive more fine-grained and personalized update alerts about fixes that are relevant to the version and features you use, please consider subscribing to MySQL Enterprise (a commercial MySQL offering). For more details please see http://www.mysql.com/products/enterprise/advisors.html.
Important Change; MySQL Cluster:
AUTO_INCREMENT columns had the following
problems when used in
AUTO_INCREMENT counter was not
updated correctly when such a column was updated.
AUTO_INCREMENT values were not
prefetched beyond statement boundaries.
AUTO_INCREMENT values were not handled
After being set,
showed a value of 1, regardless of the value it had
actually been set to.
As part of this fix, the behavior of
has changed. Setting this to less than 32 no longer has any
effect on prefetching within statements (where IDs are now
always obtained in batches of 32 or more), but only between
statements. The default value for this variable has also
changed, and is now
(Bug #25176, Bug #31956, Bug #32055)
Important Change; Replication:
When the master crashed during an update on a transactional
table while in
the slave failed. This fix causes every transaction (including
autocommit transactions) to be
recorded in the binary log as starting with a
ending with a
The current fix does not cause
nontransactional changes to be wrapped in
when written to the binary log. For this purpose, any
statements affecting tables using a nontransactional storage
engine such as
regarded as nontransactional, even when
autocommit is enabled.
References: See also Bug #29288, Bug #49522.
Important Note; Replication: Network timeouts between the master and the slave could result in corruption of the relay log. This fix rectifies a long-standing replication issue when using unreliable networks, including replication over wide area networks such as the Internet. If you experience reliability issues and see many You have an error in your SQL syntax errors on replication slaves, we strongly recommend that you upgrade to a MySQL version which includes this fix. (Bug #26489)
An improperly reset internal signal was observed as a hang when
using events in the
NDB API but
could result in various errors.
MySQL Cluster: Incorrectly handled parameters could lead to a crash in the Transaction Coordinator during a node failure, causing other data nodes to fail. (Bug #33168)
MySQL Cluster: The failure of a master node could lead to subsequent failures in local checkpointing. (Bug #32160)
Primary keys on variable-length columns (such as
VARCHAR) did not work correctly.
When inserting a row into an
table with a duplicate value for a nonprimary unique key, the
error issued would reference the wrong key.
This improves on an initial fix for this issue made in MySQL 5.0.30 and MySQL 5.0.33 (Bug #21072)
DROP USER, or
RENAME USER statement that fails
on the master, or that is a duplicate of any of these
statements, is no longer written to the binary log; previously,
either of these occurrences could cause the slave to fail.
References: See also Bug #29749.
SQL statements containing comments using
syntax were not replayable by mysqlbinlog,
even though such statements replicated correctly.
DROP VIEW statement
caused replication to fail if the view did not actually exist.
server_id did not
update its value for the current session.
The server crashed when executing a query that had a subquery
containing an equality X=Y where Y referred to a named select
list expression from the parent select. The server crashed when
trying to use the X=Y equality for
Use of uninitialized memory for
filesort in a
subquery caused a server crash.
The parser permitted control structures in compound statements to have mismatched beginning and ending labels. (Bug #33618)
SET GLOBAL myisam_max_sort_file_size=DEFAULT
to an incorrect value.
References: See also Bug #31177.
CREATE TABLE ...
SELECT created tables that for date columns used the
Field_date type instead of
References: See also Bug #33402, Bug #30617.
could not be used as views due to incorrect column reference
The fix for Bug #11230 and Bug #26215 introduced a significant input-parsing slowdown for the mysql client. This has been corrected. (Bug #33057)
UNION constructs cannot contain
INTO except in the final
SELECT. However, if a
UNION was used in a subquery and
INTO clause appeared in the top-level
query, the parser interpreted it as having appeared in the
UNION and raised an error.
The correct data type for a
resulting from a
UNION could be
determined incorrectly in some cases: 1) Not correctly inferred
NULL depending on the number of selects;
2) Not inferred correctly as
NULL if one
select used a subquery.
For queries containing
, there was a
limitation that the
col_list ORDER BY
DISTINCT columns had to
be the same as
ORDER BY columns. Incorrect
results could be returned if this was not true.
mysql-test-run.pl sometimes set up test scenarios in which the same port number was passed to multiple servers, causing one of them to be unable to start. (Bug #31880)
Name resolution for correlated subqueries and
HAVING clauses failed to distinguish which of
two was being performed when there was a reference to an outer
aliased field. This could result in error messages about a
HAVING clause for queries that had no such
Views were treated as insertable even if some base table columns with no default value were omitted from the view definition. (This is contrary to the condition for insertability that a view must contain all columns in the base table that do not have a default value.) (Bug #29477)
resolveip failed to produce correct results for host names that begin with a digit. (Bug #27427)
mysqlcheck -A -r did not correctly identify all tables that needed repairing. (Bug #25347)
For Windows Vista, MySQLInstanceConfig.exe did not include a proper manifest enabling it to run with administrative privileges. (Bug #22563)
References: See also Bug #24732.
mysqldumpslow returned a confusing error message when no configuration file was found. (Bug #20455)