End of Product Lifecycle. Active development and support for MySQL database server versions 3.23, 4.0, and 4.1 has ended. However, for MySQL 4.0 and 4.1, there is still extended support available. For details, see http://www.mysql.com/company/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/company/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 4.0 and 4.1. Please consider upgrading to a recent version (MySQL 5.0 or 5.1).
Added
--sql-mode=
option to mysqld. See
Section 5.1.2, “Command Options”.
value[,value[,value]]
Fixed possible problem with shutdown on
Solaris where the .pid file wasn't
deleted.
InnoDB now supports < 4GB rows. The
former limit was 8000 bytes.
The doublewrite file flush method is used
in InnoDB. It reduces the need for Unix
fsync() calls to a fraction and improves
performance on most Unix flavors.
You can now use the InnoDB Monitor to print
a lot of InnoDB state information,
including locks, to the standard output. This is useful in
performance tuning.
Several bugs which could cause hangs in
InnoDB have been fixed.
Split record_buffer to
record_buffer and
record_rnd_buffer. To make things
compatible to previous MySQL versions, if
record_rnd_buffer is not set, then it takes
the value of record_buffer.
Fixed optimizing bug in ORDER BY where some
ORDER BY parts where wrongly removed.
Fixed overflow bug with ALTER TABLE and
MERGE tables.
Added prototypes for my_thread_init() and
my_thread_end() to
mysql_com.h
Added --safe-user-create option to
mysqld.
Fixed bug in SELECT DISTINCT ... HAVING
that caused error message Can't find record in
#...

User Comments
Add your own comment.