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.
Rows_examined count in slow query
Fixed bug when using a reference to an
AVG() column in
Fixed that date functions that require correct dates, like
Fixed bug in const-propagation when comparing columns of
different types. (
SELECT * FROM date_col="2001-01-01"
Fixed bug that caused error message
because of unique constraint with some
GROUP BY queries.
Fixed problem with
sjis character strings
used within quoted table names.
Fixed core dump when using
FULLTEXT keys with other storage engines than
Do not use
signal() on Windows because this
appears to not be 100% reliable.
Fixed bug when doing
WHERE col_name=NULL on
an indexed column that had
Fixed bug when doing
LEFT JOIN ... ON (col_name =
constant) WHERE col_name = constant.
When using replications, aborted queries that contained
% could cause a core dump.
TCP_NODELAY was not used on some systems.
Applied portability fixes for OS/2. (Patch by Yuri Dario.)
The following changes are for
InnoDB variables to
Foreign key checking is now done for
DROP DATABASE now works also
InnoDB now supports data files and raw disk
partitions bigger than 4GB on those operating systems that
have big files.
InnoDB calculates better table cardinality
estimates for the MySQL optimizer.
Accent characters in the default character set
latin1 are ordered according to the MySQL
Note: If you are using
latin1 and have
inserted characters whose code is greater than 127 into an
CHAR column, you should
CHECK TABLE on your table
when you upgrade to 3.23.44, and drop and reimport the table
CHECK TABLE reports an
helps in performance tuning in heavily concurrent
up server shutdown.
to save your data in case the disk image of the database
innodb_monitor has been improved and a new
Increased maximum key length from 500 to 7000 bytes.
Fixed a bug in replication of
AUTO_INCREMENT columns with multiple-line
Fixed a bug when the case of letters changes in an update of an indexed secondary column.
Fixed a hang when there are more than 24 data files.
Fixed a crash when
selected from an empty table, and
not the first column in a multi-column index.
Fixed a bug in purge which could cause crashes.