Hi! InnoDB is a MySQL table type which provides transactions, row level locking, automatic crash recovery, foreign keys, and hot backup capability to MySQL. InnoDB is included in all distributions of MySQL-4.0, not just in MySQL-Max-4.0.
Since InnoDB in MySQL/InnoDB-4.0.1 was the same as InnoDB-3.23.47, I have pasted below also the changelogs of all versions 3.23.48-3.23.51. Significant new features, when compared to 4.0.1, include an option to use an auto-extending last data file: innodb_data_file_path=ibdata1:2000M;ibdata2:10M:autoextend and better support for foreign keys, including the clause ON DELETE CASCADE. For detailed information see the on-line manual at http://www.innodb.com/ibman.html. Best regards, Heikki Tuuri Innobase Oy http://www.innodb.com ......................................................................... MySQL/InnoDB-4.0.2, July 10, 2002 * InnoDB is essentially the same as InnoDB-3.23.51. * If no innodb_data_file_path is specified in my.cnf, InnoDB at the database creation now creates a 10 MB auto-extending data file ibdata1 to the datadir of MySQL. In 4.0.1 the file was 64 MB and not auto-extending. 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 [GLOBAL | SESSION] 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. MySQL/InnoDB-3.23.49, February 17, 2002 * Fixed a bug: if you called DROP DATABASE for a database on which there simultaneously were running queries, the MySQL server could crash or hang. Crashes fixed, but a full fix has to wait some changes in the MySQL layer of code. * Fixed a bug: on Windows one had to put the database name in lower case for DROP DATABASE to work. Fixed in 3.23.49: case no longer matters on Windows. On Unix the database name remains case-sensitive. * Fixed a bug: if one defined a non-latin1 character set as the default character set, then definition of foreign key constraints could fail in an assertion failure in dict0crea.c, reporting an internal error 17. MySQL/InnoDB-3.23.48, February 9, 2002 * Tuned the SQL optimizer to favor more often index searches over table scans. * Fixed a performance problem when several large SELECT queries are run concurrently on a multiprocessor Linux computer. Large CPU-bound SELECT queries will now also generally run faster on all platforms. * If MySQL binlogging is used, InnoDB now prints after crash recovery the latest MySQL binlog file name and the position in that file (= byte offset) InnoDB was able to recover to. This is useful, for example, when resynchronizing a master and a slave database in replication. * Added better error messages to help in installation problems. * One can now recover also MySQL temporary tables which have become orphaned inside the InnoDB tablespace. * InnoDB now prevents a FOREIGN KEY declaration where the signedness is not the same in the referencing and referenced integer columns. * Fixed a bug: calling SHOW CREATE TABLE or SHOW TABLE STATUS could cause memory corruption and make mysqld to crash. Especially at risk was mysqldump, because it calls frequently SHOW CREATE TABLE. * Fixed a bug: if on Unix you did an ALTER TABLE to an InnoDB table and simultaneously did queries to it, mysqld could crash with an assertion failure in row0row.c, line 474. * Fixed a bug: if inserts to several tables containing an auto-inc column were wrapped inside one LOCK TABLES, InnoDB asserted in lock0lock.c. * In 3.23.47 we allowed several NULLS in a UNIQUE secondary index. But CHECK TABLE was not relaxed: it reports the table as corrupt. CHECK TABLE no longer complains in this situation. * Fixed a bug: on Sparc and other high-endian processors SHOW VARIABLES showed innodb_flush_log_at_trx_commit and other boolean-valued startup parameters always OFF even if they were switched on. * Fixed a bug: if you ran mysqld-max-nt as a service on Windows NT/2000, the service shutdown did not always wait long enough for the InnoDB shutdown to finish. --------------------------------------------------------------------- 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
