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 problem that affected queries that did arithmetic on group functions.
Fixed problem with timestamps and
date_col BETWEEN const_date AND const_date works.
Fixed problem when only changing a 0 to
NULL in a table with
Fixed bug in range optimizer when using many key parts and or on the middle key parts:
WHERE K1=1 and K3=2 and (K2=2 and K4=4 or K2=3 and K4=5)
source command to mysql to allow reading of batch files inside the mysql client. Original patch by Matthew Vanecek.
Fixed critical problem with the
WITH GRANT OPTION option.
Do not give an unnecessary
GRANT error when using tables from many databases in the same query.
Added VIO wrapper (needed for SSL support; by Andrei Errapart and Tonu Samuel).
Fixed optimizer problem on
SELECT when using many overlapping indexes. MySQL should now be able to choose keys even better when there are many keys to choose from.
Changed optimizer to prefer a range key instead of a ref key when the range key can uses more columns than the ref key (which only can use columns with
=). For example, the following type of queries should now be faster:
SELECT * from key_part_1=const and key_part_2 > const2
Fixed bug that a change of all
VARCHAR columns to
CHAR columns didn't change row type from dynamic to fixed.
Disabled floating-point exceptions for FreeBSD to fix core dump when doing
Renamed mysqld startup option from
HEAP tables. This should fix all problems with
HEAP tables when using non-
Added option to print default arguments to all clients.
--log-slow-queries option to mysqld to log all queries that take a long time to a separate log file with a time indicating how long the query took.
Fixed core dump when doing
Fixed optimization bug in
SELECT ... LEFT JOIN ... , when
key_col IS NULL
key_col could contain
Fixed problem with 8-bit characters as separators in
LOAD DATA INFILE.