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.
Functionality added or changed:
Security improvement: Applied a patch to fix a UDF library-loading vulnerability that could result in a buffer overflow and code execution. (CVE-2005-2558)
compilation option to configure.
(Previously it was necessary to pass
-DBIG_TABLES to the compiler manually in
order to enable large table support.) See
Section 2.9.2, “Typical configure Options”, for details.
On Mac OS X,
libmysqlclient_r.a now is
--fno-common to make it possible
to link a shared two-level namespace library against
An error in the implementation of the
MyISAM compression algorithm caused
myisampack to fail with very large sets of
data (total size of all the records in a single column needed
to be >= 3 GB in order to trigger this issue). (Bug#8321)
A problem with the
caused compilation of MySQL to fail on single-processor Linux
systems running 2.6 kernels. (Bug#10364)
Fixed a problem with incorrect constant propagation resulting
in incorrect evaluation of
The test in configure to see whether
CXX specified gcc failed
if gcc was specified as a full path name.
API function, when a multi-byte character is encountered that
is illegal in the current character set, escape only the first
byte, not each byte. This avoids creating a valid character
from an invalid one. (Bug#9864; this is a backport of Bug#8378
from MySQL 4.1.11 to 4.0.25)
Fixed a bug that caused concurrent inserts to be allowed into
the tables in the
SELECT ... UNION ... part
INSERT ... SELECT ... UNION .... This
could result in the incorrect order of queries in the binary
InnoDB: Fixed a bug: MySQL-4.0.23 and 4.0.24 could complain that an InnoDB table created with MySQL-3.23.49 or earlier was in the new compact InnoDB table format of 5.0.3 or later, and InnoDB would refuse to use that table. (The same bug exists in 4.1.8 - 4.1.10.) There is nothing wrong with the table, it is mysqld that is in error. Workaround: wait that 4.0.25 or 4.1.11 is released before doing an upgrade, or dump the table and re-create it with any MySQL version >= 3.23.50 before upgrading to 4.0.23 or 4.0.24.