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:
ORDER BY clauses which updated the
same indexed column that was being filtered on were optimized
with a full index scan instead of a more appropriate index range
func_math test returned warnings
when the server was not compiled with
RPM packages had an incorrect
MBROverlaps GIS function returned
The length of a
VARCHAR() column that used
utf8 character set would increase each
time the table was re-created in a stored procedure or prepared
statement, eventually causing the
TABLE statement to fail.
A prepared statement created from a
LIKE query (such as
PREPARE stmt1 FROM
'SELECT col_1 FROM tedd_test WHERE col_1 LIKE ?';)
would begin to produce erratic results after being executed
repeatedly numerous (thousands) of times.