Hi, I have been wondering if there is a schedule when MySQL 4.x is not considered "beta/developement" anymore - www.mysql.com recommend MySQL 4.x for testing only, and has done for some time now.
Thanks and best regards Peter ----- Original Message ----- From: "Heikki Tuuri" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Wednesday, October 02, 2002 1:12 PM Subject: MySQL/InnoDB-4.0.4 is released > Hi! > > InnoDB is a table type which provides transactions, row level locking, > foreign key constraints, and a non-free hot backup tool to MySQL. > > InnoDB is included in both downloadable versions of MySQL-4.0: MySQL-Pro and > MySQL-Max. > > Release 4.0.4-beta is mainly a bug fix release. > > The changelog: > > * InnoDB again uses unbuffered disk i/o to data files in Windows. Win XP and > Win 2000 read performance seems to be very poor with normal i/o. > * Increased the max key length of InnoDB tables from 500 to 1024 bytes. > * Increased the table comment field in SHOW TABLE STATUS so that up to 16000 > characters of foreign key definitions can be printed there. > * The auto-increment counter is no longer incremented if an insert of a row > immediately fails in an error. > * Allow dropping and creating a table even if innodb_force_recovery is set. > One can use this to drop a table which would cause a crash in rollback or > purge, or if a failed table import causes a runaway rollback in recovery. > * Fixed a bug: fast shutdown (which is the default) sometimes was slowed > down by purge and insert buffer merge. > * Fixed a bug: doing a big SELECT from a table where no rows were visible in > a consistent read could cause a very long (> 600 seconds) semaphore wait in > btr0cur.c line 310. > * Fixed a bug: if the MySQL query cache was used, it did not get invalidated > by a modification done by ON DELETE CASCADE or ...SET NULL. > * Fixed a bug: if you created a temporary table inside LOCK TABLES, and used > that temporary table, that caused an assertion failure in ha_innodb.cc. > * Fixed a bug: if you set innodb_flush_log_at_trx_commit to 1, SHOW > VARIABLES would show its value as 16 million. > * Fixed a bug: Using ORDER BY primarykey DESC in 4.0.3 causes an assertion > failure in btr0pcur.c, line 203. > * An outstanding bug: SQL queries of type "WHERE indexedcolumn LIKE 'abc%' > ORDER BY indexedcolumn DESC" may return only rows where indexedcolumn='abc'. > Will be fixed in 4.0.5. > > Best regards, > > Heikki Tuuri > Innobase Oy > --- > InnoDB - transactions, hot backup, and foreign key support for MySQL > See http://www.innodb.com, download MySQL-Max from http://www.mysql.com > > > > > --------------------------------------------------------------------- > Please check "http://www.mysql.com/Manual_chapter/manual_toc.html"; before > posting. To request this thread, e-mail [EMAIL PROTECTED] > > To unsubscribe, send a message to the address shown in the > List-Unsubscribe header of this message. If you cannot see it, > e-mail [EMAIL PROTECTED] instead. > > --------------------------------------------------------------------- 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
