Hi! InnoDB is a MySQL table type which is included in all GPL versions of MySQL-4.0 that you can download from http://www.mysql.com, and is included in the commercial MySQL license MySQL Pro, which you can buy from https://order.mysql.com/?sub=pg&pg_no=1.
You can buy technical support for InnoDB from http://www.mysql.com/support/index.html. Remember that you have to buy an ADVANCED support contract WITH the InnoDB OPTION. You have to check the box on the second order page to include the InnoDB support option. InnoDB is the only MySQL table type which supports transactions, row level locking, multiversioned concurrency control, and foreign key constraints. An separate online binary hot backup tool for InnoDB can be bought from http://www.innodb.com/order.php. ... The MySQL/InnoDB version 4.0 is the stable version which is recommended for production use. Release 4.0.17 of InnoDB contains only a few bug fixes associated with column prefix secondary indexes, for example, CREATE TABLE t (a VARCHAR(255), INDEX a(10)) TYPE=InnoDB; and UPDATEs of secondary index columns when the new updated value is alphabetically equivalent, e.g., 'abcde' -> 'aBCdé'. There are several not-yet-fixed non-critical bugs in InnoDB-4.0.17. Their fixing was delayed because of the effort to release 4.1.1 earlier this month. ... The full changelog for InnoDB-4.0.17: * Fixed a bug: if you created a column prefix secondary index and updated it so that the last characters in the column prefix were spaces, InnoDB would assert in row0upd.c, line 713. The same assertion failed if you updated a column in an ordinary secondary index so that the new value was alphabetically equivalent, but had a different length. This could happen, for example, in the utf-8 character set if you updated a letter to its accented or umlaut form. * Fixed a bug: InnoDB could think that a secondary index record was not locked though it had been updated to an alphabetically equivalent value, e.g., 'abc' -> 'aBc'. * Fixed a bug: if you updated a secondary index column to an alphabetically equivalent value, and rolled back your update, InnoDB failed to restore the field in the secondary index to its original value. Best regards, Heikki Tuuri Innobase Oy http://www.innodb.com InnoDB - transactions, row level locking, and foreign keys for MySQL InnoDB Hot Backup - a hot backup tool for InnoDB which also backs up MyISAM tables -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
