This is a Monthly Rapid Update release of the MySQL Enterprise Server 5.0.
This section documents all changes and bug fixes that have been applied since the last MySQL Enterprise Server release (5.0.32).
Functionality Added or Changed
to configure. If configure
is run with this option, the
--init-file options for
mysqld are disabled and cannot be used. For
Windows, the configure.js script recognizes
DISABLE_GRANT_OPTIONS flag, which has the
now is enabled by default for binary Mac OS X distributions. Use
of thread priorities degrades performance on Mac OS X.
When a data node was shut down using the management client
STOP command, a connection event
NDB_LE_Connected) was logged instead of a
disconnection event (
MySQL Cluster: Hosts in clusters with large numbers of nodes could experience excessive CPU usage while obtaining configuration data. (Bug #25711)
Cluster API: A unique index lookup on a nonexistent tuple could lead to a data node timeout (error 4012). (Bug #25059)
method using execution type
Commit and abort
AO_IgnoreError could lead to a crash
of the transaction coordinator (
Dropping a user-defined function sometimes did not remove the
UDF entry from the
QUICK could sometimes cause one of the affected tables
to become corrupted.
CASE statements inside
stored routines could lead to excessive resource usage or a
crash of the server.
(Bug #19194, Bug #24854)
An assertion failed incorrectly for prepared statements that
contained a single-row uncorrelated subquery that was used as an
argument of the
IS NULL predicate.
Referencing an ambiguous column alias in an expression in the
ORDER BY clause of a query caused the server
A view was not handled correctly if the
SELECT part contained
Inserting a row into a table without specifying a value for a
column caused the column to be set to spaces, not zeros.
N) NOT NULL
FEDERATED storage engine did not support
utf8 character set.
Some joins in which one of the joined tables was a view could return erroneous results or crash the server. (Bug #24345)
Using a view in combination with a
clause caused column aliases to be ignored.
A crash of the MySQL Server could occur when unpacking a
BLOB column from a row in a
corrupted MyISAM table. This could happen when trying to repair
a table using either
or myisamchk; it could also happen when
trying to access such a “broken” row using
SELECT if the
table was not marked as crashed.
MyISAM table that became
corrupted could crash myisamchk and possibly
the MySQL Server.
mysqld_error.h was not installed when only
the client libraries were built.
InnoDB: Optimizations removed in MySQL 5.0.28
were re-enabled except for files under the
innobase/mem directory. (This is a
fine-tuning of optimization disabling.)
The optimizer removes expressions from
DISTINCT clauses if they
happen to participate in
WHERE 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
Optimizations that are legal only for subqueries without tables
WHERE conditions were applied for any
subquery without tables.
Instance Manager could crash during shutdown. (Bug #19044)
Changing the value of
myisam.h and recompiling MySQL resulted in
a myisamchk that saw existing
MyISAM tables as corrupt.
User-defined variables could consume excess memory, leading to a
crash caused by the exhaustion of resources available to the
MEMORY storage engine, due to the fact that
this engine is used by MySQL for variable storage and
intermediate results of
GROUP BY queries.
been used, such a condition could instead give rise to the
misleading error message You may only use constant
expressions with SET, rather than Out of
memory (Needed NNNNNN bytes).
InnoDB: During a restart of the MySQL Server
that followed the creation of a temporary table using the
InnoDB storage engine, MySQL failed to clean
up in such a way that
InnoDB still attempted
to find the files associated with such tables.
The server was built even when configure was
run with the
References: See also Bug #32898.
FEDERATED storage engine did not support
euckr character set.