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.14 Changes in Release 3.23.46 (29 November 2001)
B.3.15 Changes in Release 3.23.45 (22 November 2001) »
Section Navigation      [Toggle]

B.3.14. Changes in Release 3.23.46 (29 November 2001)

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).

  • Fixed problem with aliased temporary table replication.

  • InnoDB and BDB tables now use index when doing an ORDER BY on the whole table.

  • Fixed bug where one got an empty set instead of a DEADLOCK error when using BDB tables.

  • One can now kill ANALYZE TABLE, REPAIR TABLE, and OPTIMIZE TABLE when the thread is waiting to get a lock on the table.

  • Fixed race condition in ANALYZE TABLE.

  • Fixed bug when joining with caching (unlikely to happen).

  • Fixed race condition when using the binary log and INSERT DELAYED which could cause the binary log to have rows that were not yet written to MyISAM tables.

  • Changed caching of binary log to make replication slightly faster.

  • Fixed bug in replication on Mac OS X.


User Comments

Posted by [name withheld] on June 17 2002 3:39pm[Delete] [Edit]

A useful index to the updates may be found at <a
href='http://www.bitbybit.dk/mysqlfaq'>http://www.
bitbybit.dk/mysqlfaq</a>. This index contains the
changes grouped by concept, making it easy to
find out when a particular feature/bug was
added/fixed.

Posted by Najmi Thayyil on June 17 2002 3:39pm[Delete] [Edit]

It is great..really great...We are expecting
mysql will update itslf by forseeing new demands
and hence to support your large customer base.
And also expecting a new mysql version with full
support for Foreign Key

Posted by Stephen VanDyke on June 17 2002 3:39pm[Delete] [Edit]

Good job guys, I always enjoy new releases. My
only wishlist item is for speed improvements on
super huge tables (1M+ records). "DELETE FROM
table WHERE keycolumn='someval'" really could use
some speed improvement. Also it would be cool if
there was a way to force OPTIMIZE for some
deletes so it's not an extra command to clean out
the rows flagged for removal.

Add your own comment.