Hi! The download mirrors at www.mysql.com for the MySQL-Max version 3.23.51 do not work yet, but let us hope the mirrors get up to date in a few hours.
InnoDB is a table type in MySQL which provides transactions, foreign key constraints, and for which there exists a non-locking hot backup utility. InnoDB type tables are available in MySQL-Max-3.23 and MySQL-4.0. I list below the changes for both the version 3.23.50 and 3.23.51, because 3.23.50 never was published on the front page of www.mysql.com. The emphasis in 3.23.50 was to improve the support for foreign keys. Also the auto-extending data file is a feature which many had requested. MySQL/InnoDB-3.23.51, June 12, 2002 * Fixed a bug: a join could result in a seg fault in copying of a BLOB or TEXT column if some of the BLOB or TEXT columns in the table contained SQL NULL values. * Fixed a bug: if you added self-referential foreign key constraints with ON DELETE CASCADE to tables and a row deletion caused InnoDB to attempt the deletion of the same row twice because of a cascading delete, then you got an assertion failure. * Fixed a bug: if you use MySQL 'user level locks' and close a connection, then InnoDB may assert in ha_innobase.cc, line 302. MySQL/InnoDB-3.23.50, April 23, 2002 * InnoDB now supports an auto-extending last data file. You do not need to preallocate the whole data file at the database startup. * Made several changes to facilitate the use of the InnoDB Hot Backup tool. It is a separate non-free tool you can use to take online backups of your database without shutting down the server or setting any locks. * If you want to run the InnoDB Hot Backup tool on an auto-extending data file you have to upgrade it to version ibbackup-0.35. * The log scan phase in crash recovery will now run much faster. * Starting from this server version, the hot backup tool truncates unused ends in the backup InnoDB data files. * To allow the hot backup tool to work, on Windows we no longer use unbuffered i/o or native async i/o; instead we use the same simulated async i/o as on Unix. * You can now define the ON DELETE CASCADE or ON DELETE SET NULL clause on foreign keys. * FOREIGN KEY constraints now survive ALTER TABLE and CREATE INDEX. * We suppress the FOREIGN KEY check if any of the column values in the foreign key or referenced key to be checked is the SQL NULL. This is compatible with Oracle, for example. * SHOW CREATE TABLE now lists also foreign key constraints. Also mysqldump no longer forgets about foreign keys in table definitions. * You can now add a new foreign key constraint with ALTER TABLE ... ADD CONSTRAINT FOREIGN KEY (...) REFERENCES ... (...). * FOREIGN KEY definitions now allow backquotes around table and column names. * MySQL command SET TRANSACTION ISOLATION LEVEL ... has now the following effect on InnoDB tables: if a transaction is defined as SERIALIZABLE then InnoDB conceptually adds LOCK IN SHARE MODE to all consistent reads. If a transaction is defined to have any other isolation level, then InnoDB obeys its default locking strategy which is REPEATABLE READ. * SHOW TABLE STATUS no longer sets an x-lock at the end of an auto-increment index if the auto-increment counter has already been initialized. This removes in almost all cases the surprising deadlocks caused by SHOW TABLE STATUS. * Fixed a bug: in a CREATE TABLE statement the string 'foreign' followed by a non-space character confused the FOREIGN KEY parser and caused table creation to fail with errno 150. Best regards, Heikki Tuuri Innobase Oy --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
