Hi! InnoDB is a MySQL table type which provides ACID transactions, row-level locking, consistent, non-locking SELECTs (MVCC concurrency control), FOREIGN KEY constraints with CASCADE options, and a commercial hot backup tool.
Release 4.1.5 is mainly a bugfix release. InnoDB bug fixing is lagging behind after the summer vacation season, and there are a few important outstanding bugs in 4.1.5. See below about them. The full InnoDB changelog Functionality added: * Added configuration option innodb_autoextend_increment for setting the size in megabytes by which InnoDB tablespaces are extended when they become full. The default value is 8, corresponding to the fixed increment of 8MB in previous versions of MySQL. Bugs fixed: * Fixed a bug that InnoDB only allowed a maximum of 1000 connections inside InnoDB at the same time. A higher number could cause an assertion failure in sync0arr.c, line 384. Now we allow 1000, 10000, or 50000, depending on the buffer pool size. (Bug #5414) Outstanding bugs: * If you use the my.cnf option innodb_file_per_table, you cannot create TEMPORARY InnoDB type tables, unless you add a database 'tmp' (in Windows 'temp') to your MySQL installation. * Column prefix indexes, where only an initial prefix of a column is taken to an index, do not work yet properly in the UTF-8 character set. Upgrading from earlier MySQL versions: * If you have created or used InnoDB tables with TIMESTAMP columns in MySQL versions 4.1.0-4.1.3, you have to rebuild those tables when you upgrade to MySQL-4.1.4 or later. The storage format in those MySQL versions for a TIMESTAMP column was wrong. If you upgrade from 4.0 to 4.1.4 or later, then no rebuild of TIMESTAMP tables is needed. * If you have stored characters < ASCII(32) to non-latin1 non-BINARY indexed columns in MySQL versions <= 4.1.2, then you have to rebuild those tables after you upgrade to >= 4.1.3. The reason is that the sorting order of those characters and the space character changes for some character sets in 4.1.3. See the MySQL/InnoDB-4.1.3 changelog for a precise description of the cases where you need to rebuild the table (also MyISAM tables need a rebuild in these cases). 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]
