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.
Important Change: Some changes were made to
CHECK TABLE ... FOR UPGRADEand
REPAIR TABLEwith respect to detection and handling of tables with incompatible
.frmfiles (files created with a different version of the MySQL server). These changes also affect mysqlcheck because that program uses
REPAIR TABLE, and thus also mysql_upgrade because that program invokes mysqlcheck.
If your table was created by a different version of the MySQL server than the one you are currently running,
CHECK TABLE ... FOR UPGRADEindicates that the table has an
.frmfile with an incompatible version. In this case, the result set returned by
CHECK TABLEcontains a line with a
Table upgrade required. Please do "REPAIR TABLE `
tbl_name`" to fix it!
.frmfile to the current version.
If you use
REPAIR TABLE ...USE_FRMand your table was created by a different version of the MySQL server than the one you are currently running,
REPAIR TABLEwill not attempt to repair the table. In this case, the result set returned by
REPAIR TABLEcontains a line with a
Failed repairing incompatible .FRM file.
Previously, use of
REPAIR TABLE ...USE_FRMwith a table created by a different version of the MySQL server risked the loss of all rows in the table.
mysql_upgrade now has a
--tmpdiroption to enable the location of temporary files to be specified. (Bug #36469)
Important Change: The server no longer issues warnings for truncation of excess spaces for values inserted into
CHARcolumns. This reverts a change in the previous release that caused warnings to be issued. (Bug #30059)
CREATE VIEWstatements 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 log. (Bug #32575)
References: See also Bug #36570.
mysqltest ignored the value of
--tmpdirin one place. (Bug #36465)
Conversion of a
FLOAT ZEROFILLvalue to string could cause a server crash if the value was
NULL. (Bug #36139)
An error in calculation of the precision of zero-length items (such as
NULL) caused a server crash for queries that employed temporary tables. (Bug #36023)
The server crashed inside
NOT INsubqueries with an impossible
HAVINGclause, such as
NOT IN (SELECT ... FROM t1, t2, ... WHERE 0). (Bug #36005)
SET GLOBAL debug=''resulted in a Valgrind warning in
DbugParse(), which was reading beyond the end of the control string. (Bug #35986)
The combination of
LEFT JOINcould crash the server when the right table is empty. (Bug #35298)
Several additional configuration scripts in the
BUILDdirectory 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.) (Bug #34291)
init_time()library function was renamed to
my_init_time()to avoid conflicts with external libraries. (Bug #26294)
The parser used signed rather than unsigned values in some cases that caused legal lengths in column declarations to be rejected. (Bug #15776)