End of Product LifecycleActive development and support for MySQL Database Server versions 3.23, 4.0, and 4.1 has ended. For details, see http://www.mysql.com/about/legal/lifecycle/#calendar. Please consider upgrading to a recent version. Further updates to the content of this manual will be minimal. All formats of this manual will continue to be available until 31 Dec 2010.
Fixed problem in alarm handling that could cause problems when getting a packet that is too large.
Fixed problem when installing MySQL as a service on Windows when two arguments were specified to mysqld (option file group name and service name).
kill pid-of-mysqld to work on Mac OS
SHOW VARIABLES LIKE 'innodb_data_file_path'
displayed only the name of the first data file. (Bug #468)
Fixed unlikely problem in optimizing
clause with a constant expression such as in
AND (a=1 AND b=1).
Fixed problem on IA-64 with timestamps that caused mysqlbinlog to fail.
The default option for
was changed from 0 to 1 to make
tables ACID by default. See
Section 13.2.4, “
InnoDB Startup Options and System Variables”.
Fixed problem with too many allocated alarms on slave when connecting to master many times (normally not a very critical error).
Fixed a bug in replication of temporary tables. (Bug #183)
Fixed 64-bit bug that affected at least AMD hammer systems.
Fixed a bug when doing
LOAD DATA INFILE
IGNORE: When reading the binary log,
mysqlbinlog and the replication code read
REPLACE instead of
IGNORE. This could make the slave's table
become different from the master's table. (Bug #218)
Fixed overflow bug in
MyISAM when a row is
inserted into a table with a large number of columns and at
BLOB/TEXT column. Bug was caused
by incorrect calculation of the needed buffer to pack data.
The binary log was not locked during
which could cause an
tbl_name to be written to the log
TRUNCATE TABLE or
Fixed rare bug in
InnoDB tables where one row could be
updated multiple times.
Produce an error for empty table and column names.
PROCEDURE ANALYSE() to report
DATE instead of
PROCEDURE ANALYSE(#) to restrict
the number of values in an
# also for string values.
mysqldump no longer silently deletes the
binary logs when invoked with the
--first-slave option; while
this behavior was convenient for some users, others may suffer
from it. Now you must explicitly ask for binary logs to be
deleted by using the new