End of Product Lifecycle. Active development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).
Fixed double free'd pointer bug in
mysql_change_user() handling,
that enabled a specially hacked version of MySQL client to
crash mysqld. Note that you must log in to
the server by using a valid user account to be able to exploit
this bug. (CVE-2003-0073)
Fixed bug with the --slow-log when logging an
administrator command (like FLUSH TABLES).
Fixed bug in GROUP BY when used on BLOB
column with NULL values.
Fixed a bug in handling NULL values in
CASE ... WHEN ....
Bugfix for --chroot (see
Section B.3.6, “Changes in release 3.23.54 (05 December 2002)”) is reverted. Unfortunately,
there is no way to make it to work, without introducing
backward-incompatible changes in my.cnf.
Those who need --chroot functionality, should
upgrade to MySQL 4.0. (The fix in the 4.0 branch did not break
backward-compatibility).
Make --lower-case-table-names default on Mac
OS X as the default filesystem (HFS+) is case insensitive.
Fixed a bug in scripts/mysqld_safe.sh in
NOHUP_NICENESS testing.
Transactions in AUTOCOMMIT=0 mode didn't
rotate binary log.
Fixed a bug in
scripts/make_binary_distribution that
resulted in a remaining @HOSTNAME@ variable
instead of replacing it with the correct path to the
hostname binary.
Fixed a very unlikely bug that could cause SHOW
PROCESSLIST to core dump in pthread_mutex_unlock()
if a new thread was connecting.
Forbid SLAVE STOP if the thread executing
the query has locked tables. This removes a possible deadlock
situation.

User Comments
Add your own comment.