This is a Monthly Rapid Update release of the MySQL Enterprise Server 5.0.
After release, a trigger failure problem was found to have been introduced. (Bug#27006) Users affected by this issue should upgrade to MySQL 5.0.38, which corrects the problem.
Functionality added or changed:
Incompatible Change: MySQL Cluster:
The LockPagesInMainMemory
configuration
parameter has changed its type and possible values. For more
information, see
LockPagesInMainMemory
.
The values true
and
false
are no longer accepted for this
parameter. If you were using this parameter and had it set to
false
in a previous release, you must
change it to 0
. If you had this parameter
set to true
, you should instead use
1
to obtain the same behavior as
previously, or 2
to take advantage of new
functionality introduced with this release, as described in
the section cited above.
Incompatible Change:
Previously, the DATE_FORMAT()
function returned a binary string. Now it returns a string with
a character set and collation given by
character_set_connection
and
collation_connection
so that it
can return month and weekday names containing non-ASCII
characters.
(Bug#22646)
Bugs fixed:
Security Fix:
Using an INFORMATION_SCHEMA
table with
ORDER BY
in a subquery could cause a server
crash.
We would like to thank Oren Isacson of Flowgate Security Consulting and Stefan Streichsbier of SEC Consult for informing us of this problem. (Bug#24630, Bug#26556, CVE-2007-1420)
Incompatible Change:
For ENUM
columns that had
enumeration values containing commas, the commas were mapped to
0xff
internally. However, this rendered the
commas indistinguishable from true 0xff
characters in the values. This no longer occurs. However, the
fix requires that you dump and reload any tables that have
ENUM
columns containing any true
0xff
values. Dump the tables using
mysqldump with the current server before
upgrading from a version of MySQL 5.0 older than 5.0.36 to
version 5.0.36 or newer.
(Bug#24660)