Documentation Home
MySQL 5.0 Release Notes
Related Documentation Download these Release Notes
PDF (US Ltr) - 2.1Mb
PDF (A4) - 2.1Mb
EPUB - 0.6Mb

MySQL 5.0 Release Notes  /  Changes in MySQL Enterprise 5.0.66 [MRU] (2008-07-09)

Changes in MySQL Enterprise 5.0.66 [MRU] (2008-07-09)

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.64). 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


This release was withdrawn from production due to the side effect produced by Bug #20748. It has been replaced by MySQL 5.0.66a, which should be used instead.

Functionality Added or Changed

  • now supports --client-bindir and --client-libdir options for specifying the directory where client binaries and libraries are located. (Bug #34995)

Bugs Fixed

  • Incompatible Change: An additional correction to the original MySQL 5.0.64 fix was made to normalize directory names before adding them to the list of directories. This prevents /etc/ and /etc from being considered different, for example. (Bug #20748)

    References: See also Bug #38180.

  • Replication: Some kinds of internal errors, such as Out of memory errors, could cause the server to crash when replicating statements with user variables.

    certain internal errors. (Bug #37150)

  • Some binary distributions had a duplicate -64bit suffix in the file name. (Bug #37623)

  • The mysql client failed to recognize comment lines consisting of -- followed by a newline. (Bug #36244)

  • An empty bit-string literal (b'') caused a server crash. Now the value is parsed as an empty bit value (which is treated as an empty string in string context or 0 in numeric context). (Bug #35658)

  • mysqlbinlog left temporary files on the disk after shutdown, leading to the pollution of the temporary directory, which eventually caused mysqlbinlog to fail. This caused problems in testing and other situations where mysqlbinlog might be invoked many times in a relatively short period of time. (Bug #35543)

  • The code for detecting a byte order mark (BOM) caused mysql to crash for empty input. (Bug #35480)

  • The mysql client incorrectly parsed statements containing the word delimiter in mid-statement.

    The fix for this bug had the side effect of causing the problem reported in Bug #38158, so it was reverted in MySQL 5.0.67. (Bug #33812)

Download these Release Notes
PDF (US Ltr) - 2.1Mb
PDF (A4) - 2.1Mb
EPUB - 0.6Mb