End of Product Lifecycle. Active 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 mysqld crash on extremely small values of
Fixed a bug in privilege system for
GRANT UPDATE on the column level.
Fixed a rare bug when using a date in
Fixed checking of random part of
WHERE clause. (Bug #142)
Fixed MySQL (and myisamchk) crash on artificially corrupted
Security enhancement: mysqld no longer reads options from world-writable config files. (CVE-2003-0150)
Security enhancement: mysqld and safe_mysqld now use only the first
--user option specified on the command line. Normally this comes from
Security enhancement: Do not allow
BACKUP TABLE to overwrite existing files.
Fixed unlikely deadlock bug when one thread did a
LOCK TABLE and another thread did a
DROP TABLE. In this case one could do a
KILL on one of the threads to resolve the deadlock.
LOAD DATA INFILE was not replicated by slave if
replicate_*_table was set on the slave.
Fixed a bug in handling
CHAR(0) columns that could cause incorrect results from the query.
Fixed a bug in
SHOW VARIABLES on 64-bit platforms. The bug was caused by incorrect declaration of variable
Comment column in
SHOW TABLE STATUS now reports that it can contain
NULL values (which is the case for a crashed
rpl_rotate_logs test to not fail on certain platforms (such as Mac OS X) due to a too-long file name (changed
Fixed a problem with
BLOB NOT NULL columns used with
Fixed bug in
MAX() optimization in
RAND() initialization for new connections.
Fixed bug with connect timeout. This bug was manifested on OS's with
poll() system call, which resulted in timeout the value specified as it was executed in both
Fixed bug in
SELECT * FROM table WHERE datetime1 IS NULL OR datetime2 IS NULL.
Fixed bug in using aggregate functions as argument for
When running with
--lower-case-table-names=1 (default on Windows) and you had tables or databases with mixed case on disk, then executing
SHOW TABLE STATUS followed with
DROP DATABASE or
DROP TABLE could fail with
Fixed bug in logging to binary log (which affects replication) a query that inserts a
NULL in an
auto_increment field and also uses
Fixed bug in mysqladmin --relative.
On some 64-bit systems,
show status reported a strange number for