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.60). 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.
Functionality Added or Changed
Some changes were made to
CHECK TABLE ... FOR
TABLE with respect to detection and handling of tables
.frm files (files created
with a different version of the MySQL server). These changes
also affect mysqlcheck because that program
CHECK TABLE and
REPAIR TABLE, and thus also
mysql_upgrade because that program invokes
If your table was created by a different version of the
MySQL server than the one you are currently running,
CHECK TABLE ...
FOR UPGRADE indicates that the table has an
.frm file with an incompatible version.
In this case, the result set returned by
CHECK TABLE contains a line
Msg_type value of
error and a
Table upgrade required. Please do "REPAIR
tbl_name`" to fix
REPAIR TABLE without
USE_FRM upgrades the
.frm file to the current version.
If you use
REPAIR TABLE ...USE_FRM and
your table was created by a different version of the MySQL
server than the one you are currently running,
REPAIR TABLE will not attempt
to repair the table. In this case, the result set returned
REPAIR TABLE contains a
line with a
Msg_type value of
error and a
Failed repairing incompatible .FRM
Previously, use of
...USE_FRM with a table created by a different
version of the MySQL server risked the loss of all rows in
mysql_upgrade now has a
--tmpdir option to enable
the location of temporary files to be specified.
The server no longer issues warnings for truncation of excess
spaces for values inserted into
CHAR columns. This reverts a
change in the previous release that caused warnings to be
CREATE VIEW statements containing
extended comments were not written to the binary log correctly,
causing parse errors on the slave. Now, all comments are
stripped from such statements before being written to the binary
References: See also Bug #36570.
mysqltest ignored the value of
--tmpdir in one place.
Conversion of a
FLOAT ZEROFILL value to
string could cause a server crash if the value was
The server crashed inside
NOT IN subqueries
with an impossible
HAVING clause, such as
(SELECT ... FROM t1, t2, ... WHERE 0).
An error in calculation of the precision of zero-length items
NULL) caused a server crash for
queries that employed temporary tables.
Several additional configuration scripts in the
BUILD directory now are included in source
distributions. These may be useful for users who wish to build
MySQL from source. (See
Installing MySQL Using a Development Source Tree, for information
about what they do.)
SET GLOBAL debug='' resulted in a Valgrind
DbugParse(), which was reading
beyond the end of the control string.
The combination of
could crash the server when the right table is empty.
init_time() library function
was renamed to
my_init_time() to avoid
conflicts with external libraries.
The parser used signed rather than unsigned values in some cases that caused legal lengths in column declarations to be rejected. (Bug #15776)