MySQL/InnoDB-5.0.4 is released

Hi!

Greetings to all from the MySQL Users Conference 2005 in Santa Clara! The
conference has just kicked off with tutorials, and will last till Thursday.
Close to 1000 people are expected to attend the conference.

MySQL-5.0 is probably the most important new MySQL release in several years.
On the MySQL side, a vast number of new features, like stored procedures and
views have been implemented in 5.0. On the InnoDB side, we changed the table
format to a more space-saving one, and implemented the 2-phase commit XA
protocol.

MySQL-5.0.4 is a bugfix release. Since MySQL-5.0.3 introduced a large number
of new features, we cannot yet recommend the MySQL 5.0 series for production
use. This is a beta release for testing and developing your applications
that take advantage of MySQL's new powerful features.

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.

You can download MySQL-5.0.4 from
http://dev.mysql.com/downloads/mysql/5.0.html

Bugs fixed:

* ENUM and SET columns were treated incorrectly as character strings. This
bug did not manifest itself with latin1 collations if there were less than
about 100 elements in an enum, but it caused malfunction with UTF-8. Old
tables will continue to work. In new tables, ENUM and SET will be internally
stored as unsigned integers. (Bug #9526)

* Avoid test suite failures caused by a locking conflict between two server
instances at server shutdown/startup. This conflict on advisory locks
appears to be the result of a bug in the operating system; these locks
should be released when the files are closed, but somehow that does not
always happen immediately in Linux. (Bug #9381)

* True VARCHAR in 5.0.3: InnoDB stored the 'position' of a row wrong in a
column prefix primary key index; this could cause MySQL to complain 'ERROR
1032: Can't find record' in an update of the primary key, and also some
ORDER BY or DISTINCT queries. (Bug #9314)

Upgrading from 4.1:

* 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.

* 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. This bug is also present in 4.0 and 4.1.

* 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/mysql?unsub=gcdmg-mysql@m.gmane.org