Hi!
InnoDB is the MySQL table type that supports transactions, FOREIGN KEY constraints, row-level locking, non-locking consistent reads, and a non-free Hot Backup utility.
Release 4.0.23 is a bugfix release of the stable MySQL-4.0 branch. This release fixes the critical hang bug of mysqld in MySQL-4.0.22 (or 4.1.7) that would occur after two runs of the innobackup-1.0 Perl script; innobackup-1.1.0 is immune to the bug in MySQL-4.0.22.
I would like to wish all MySQL users Happy Holidays and a Prosperous New Year 2005!
Functionality added or changed:
* Do not periodically write SHOW INNODB STATUS information to a temporary file unless the configuration option innodb_status_file=1 is set.
* Made the foreign key parser better aware of quotes. (Bug #6340)
Bugs Fixed:
* A sequence of BEGIN (or SET AUTOCOMMIT=0), FLUSH TABLES WITH READ LOCK, transactional update, COMMIT, FLUSH TABLES WITH READ LOCK could hang the connection forever and possibly the MySQL server itself. This happened for example when running the innobackup script several times. (Bug #6732)
* Fixed a bug in LOAD DATA INFILE.REPLACE printing duplicate key error when executing the same load query several times. (Bug #5835)
* Refuse to open new-style tables created with MySQL 5.0.3 or later. (Bug #7089)
* Do not call rewind() when displaying SHOW INNODB STATUS information on stderr.
* If one used INSERT IGNORE to insert several rows at a time, and the first inserts were ignored because of a duplicate key collision, then InnoDB in a replication slave assigned AUTO_INCREMENT values 1 bigger than in the master. This broke the MySQL replication. (Bug #6287)
* Fix two hangs: FOREIGN KEY constraints treated table and database names as case-insensitive. RENAME TABLE t TO T would hang in an endless loop if t had a foreign key constraint defined on it. Fix also a hang over the dictionary mutex that would occur if one tried in ALTER TABLE or RENAME TABLE to create a foreign key constraint name that collided with another existing name. (Bug #3478)
* Treat character 0xA0 as space in InnoDB's FOREIGN KEY parser if MySQL treats it as space in the default charset. EMS MySQL Manager inserts character 0xA0 after the table name in an ALTER, which confused InnoDB's parser.
* If a connection had an open transaction but had done no updates to transactional tables (for example if had just done a SELECT FOR UPDATE), then executed a non-transactional update, that update automatically committed the transaction (thus releasing InnoDB's row-level locks etc). (Bug #5714)
Best regards,
Heikki Tuuri http://www.innodb.com
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
