Hi!
InnoDB is the MySQL table type that supports foreign key constraints,
transactions, two-phase commit in XA, row-level locking, non-locking
consistent read (MVCC), all four SQL-1992 isolation levels of transactions,
multiple tablespaces, asynchronous unbuffered disk I/O on Windows, and a
non-free hot online backup tool.
MySQL-5.0.6 is a bugfix release of the 5.0 branch. The release is still
labeled as beta, because 5.0 contains many new features, and more real-world
testing is needed.
You can download MySQL-5.0.6 from
http://dev.mysql.com/downloads/mysql/5.0.html
Functionality added or changed:
* When the maximum length of SHOW INNODB STATUS output would be exceeded,
truncate the beginning of the list of active transactions, instead of
truncating the end of theoutput. (Bug #5436)
* If innodb_locks_unsafe_for_binlog option is set and the isolation level of
the transaction is not set to serializable then InnoDB uses a consistent
read for select in clauses like INSERT INTO ... SELECT and UPDATE ...
(SELECT) that do not specify FOR UPDATE or IN SHARE MODE. Thus no locks are
set to rows read from selected table.
Bugs fixed:
* MyISAM and InnoDB tables created with DECIMAL or NUMERIC columns in MySQL
5.0.3 to 5.0.5 will appear corrupt after an upgrade to MySQL 5.0.6. Dump
suchtables with mysqldump before upgrading, and then reload them after
upgrading. (The same incompatibility will occur for these tables created in
MySQL 5.0.6 after a downgrade to MySQL 5.0.3 to 5.0.5.) (Bug #10465, Bug
#10625)
* Fixed a critical bug in InnoDB @code{AUTO_INCREMENT}: it could assign the
same value for several rows. (Bug #10359)
* All InnoDB bug fixes from 4.1.12 and earlier versions, and also the fixes
to bugs #10335 and #10607 listed in the 4.1.13 change notes.
Upgrading from 4.1:
* MyISAM and InnoDB tables created with DECIMAL or NUMERIC columns in MySQL
5.0.3 to 5.0.5 will appear corrupt after an upgrade to MySQL 5.0.6. Dump
such tables with @command{mysqldump} before upgrading, and then reload them
after upgrading.
* Starting from 5.0.3, a VARCHAR in MySQL is a 'true' VARCHAR. It remembers
the number of spaces that there were at the end of the string. Previously,
MySQL at storage trimmed end spaces from a VARCHAR. Tables created with <
5.0.3 will remain to have the old VARCHAR semantics, while new tables will
have the new semantics.
* The sorting order for end-space in TEXT columns for InnoDB and MyISAM
tables has changed. Starting from 5.0.3, InnoDB compares TEXT columns as
space-padded at the end. If you have a non-unique index on a TEXT column,
you should run CHECK TABLE on it, and run OPTIMIZE TABLE if the check
reports errors. If you have a UNIQUE INDEX on a TEXT column, you should
rebuild the table with OPTIMIZE TABLE.
* The sorting order of BINARY and VARBINARY may still change in some 5.0.x
version.
* In 4.0 - 4.1.11 there is a bug in the InnoDB sorting order of ENUMs if the
collation of the ENUM is not latin1 or if there are more than about 100
different values for the ENUM.
* InnoDB Hot Backup 2.0.1 or earlier does not work with MySQL-5.0.3 or
later. A new version 2.1 will.
Best regards,
Heikki Tuuri
Innobase Oy
http://www.innodb.com
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
