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.
Fixed a bug that permitted use of database names containing a
.” character. This fixes a
serious security issue when mysqld is run
as root. (CVE-2001-0407)
Fixed bug when thread creation failed (could happen when doing a lot of connections in a short time).
Fixed some problems with
TEMPORARY tables. (Problem with freeing
the key cache and error
Fixed a problem in
InnoDB with other
character sets than
latin1 and another
problem when using many columns.
Fixed bug that caused a core dump when using a very complex
DISTINCT and summary
TRANSACTION ISOLATION LEVEL statement.
FOR UPDATE for
Fixed a bug where the number of affected rows was not returned when MySQL was compiled without transaction support.
Fixed a bug in
keys were not always used to find the rows to be updated.
Fixed a bug in
where it returned incorrect results.
CREATE ... SELECT and
SELECT to not allow concurrent inserts as this could
make the binary log hard to repeat. (Concurrent inserts are
enabled if you are not using the binary or update log.)
Changed some macros to be able to use fast mutex with