Skip navigation links
MySQL 3.23, 4.0, 4.1 Reference Manual :: B MySQL Change History :: B.3 Changes in Release 3.23.x :: B.3.1 Changes in Release 3.23.59 (Not yet released)
B.3.2 Changes in Release 3.23.58 (11 September 2003) »
Section Navigation      [Toggle]

B.3.1. Changes in Release 3.23.59 (Not yet released)

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 an old bug in concurrent accesses to MERGE tables (even one MERGE table and MyISAM tables), that could've resulted in a crash or hang of the server. (Bug#2408, CVE-2004-0837)

  • Fixed incorrect destruction of expression which led to crash of server on complex AND/OR expressions if query was ignored (either by a replication server because of --replicate-*-table rules, or by any MySQL server because of a syntax error). (Bug#3969, Bug#4494)

  • Fixed problem with parsing complex queries on 64-bit architectures. (Bug#4204)

  • Fixed a symlink vulnerability in the mysqlbug script. (Bug#3284, CVE-2004-0381)

  • Fixed bug in privilege checking of ALTER TABLE RENAME. (Bug#3270, CVE-2004-0835)

  • Fixed bugs in ACOS(), ASIN() (Bug#2338) and in FLOOR() (Bug#3051). The cause of the problem is an overly strong optimization done by gcc in this case.

  • Fixed bug in INSERT ... SELECT statements where, if a NOT NULL column is assigned a value of NULL, the following columns in the row might be assigned a value of zero. (Bug#2012)

  • If a query was ignored on the slave (because of --replicate-ignore-table and other similar rules), the slave still checked if the query got the same error code (0, no error) as on the master. So if the master had an error on the query (for example, “Duplicate entry” in a multiple-row insert), then the slave stopped and warned that the error codes didn't match. This is a backport of the fix for MySQL 4.0. (Bug#797)

  • mysqlbinlog now asks for a password at console when the -p/--password option is used with no argument. This is how the other clients (mysqladmin, mysqldump..) behave. Note that one now has to use mysqlbinlog -p<my_password>; mysqlbinlog -p <my_password> does not work anymore (in other words, put no space after -p). (Bug#1595)

  • On some 64-bit machines (some HP-UX and Solaris machines), a slave installed with the 64-bit MySQL binary could not connect to its master (it connected to itself instead). (Bug#1256, Bug#1381)

  • Fixed a Windows-specific bug present since MySQL 3.23.57 and 3.23.58 that caused Windows slaves to crash when they started replication if a master.info file existed. (Bug#1720)

  • Fixed bug in ALTER TABLE RENAME, when rename to the table with the same name in another database silently dropped destination table if it existed. (Bug#2628)

  • Fixed potential memory overrun in mysql_real_connect() (which required a compromised DNS server and certain operating systems). (Bug#4017, CVE-2004-0836)