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.
<> to work properly with
CREATE TEMPORARY TABLE IF NOT EXISTS
not to produce an error if the table exists.
If you don't create a
PRIMARY KEY in a
BDB table, a hidden
KEY is created.
Added read-only-key optimization to
LEFT JOIN in some cases preferred a full
table scan when there was no
don't count the time waiting for a lock.
Fixed bug in lock code on Windows which could cause the key cache to report that the key file was crashed even if it was okay.
Fixed mutex bug in the binary replication log --- long update queries could be read only in part by the slave if it did it at the wrong time, which was not fatal, but resulted in a performance-degrading reconnect and a scary message in the error log.
Changed the format of the binary log --- added magic number, server version, binary log version. Added the server ID and query error code for each query event.
Replication thread from the slave now kills all the stale threads from the same server.
Long replication user names were not being handled properly.
Updates that generated an error code (such as
INTO foo(some_key) values (1),(1)) erroneously
terminated the slave thread.
Added optimization of queries where
DISTINCT is used only on columns from some
of the tables.
Permit floating-point numbers where there is no sign after the
SHOW GRANTS didn't always show
all column grants.
option to all MySQL clients.
Columns referenced in
statements now are initialized properly.
UPDATE didn't always work when
used with a range on a timestamp that was part of the key that
was used to find rows.
Fixed a bug in
FULLTEXT index when
Changed to use
mkstemp() instead of
tempnam(). Based on a patch from John