Date: Sun, 30 Nov 2008 18:28:51 -0500 From: madodel Subject: [VOICENWS] SW: MySQL Server 5.1.30 has been released ++ From the VOICE OS/2-eCS News Service http://www.os2voice.org ++ From: Paul Smedley Hi All, MySQL v5.1 has finally made it out of beta/RC status and is GA. I've built an OS/2 version, and it's available now from http://os2ports.smedley.info Enjoy! Cheers, Paul -------- Original Message -------- Subject: MySQL Server 5.1.30 has been released Date: Thu, 27 Nov 2008 00:33:22 -0700 From: Timothy Smith Dear MySQL users, We are proud to present to you the MySQL Server 5.1.30 GA release, the first 5.1 production version of the popular open source database. MySQL 5.1.30 is recommended for use on production systems. MySQL 5.1 provides a number of new enhancements including: - Table and index partitioning - Row-based and mixed replication - Built-in job scheduler - Improved XML handling with XPath support - New SQL diagnostic aids and performance utilities - The return of the embedded library (libmysqld) For a more complete look at what's new in MySQL 5.1, please see http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html For information on installing MySQL 5.1.30 on new servers or upgrading to MySQL 5.1.30 from previous MySQL releases, please see http://dev.mysql.com/doc/refman/5.1/en/installing.html MySQL Server is available in source and binary form for a number of platforms from our download pages at http://dev.mysql.com/downloads/ Not all mirror sites may be up to date at this point in time, so if you can't find this version on some mirror, please try again later or choose another download site. We welcome and appreciate your feedback, bug reports, bug fixes, patches, etc.: http://forge.mysql.com/wiki/Contributing For information on open issues in MySQL 5.1, please see the errata list at http://dev.mysql.com/doc/refman/5.1/en/open-bugs.html The following section lists the changes in the MySQL source code since the previous released version of MySQL 5.1. It may also be viewed online at http://dev.mysql.com/doc/refman/5.1/en/news-5-1-30.html Sincerely, Kent Boortz The MySQL build team at Sun Microsystems ======================================================================= Bugs fixed: * Partitioning: A SELECT using a range WHERE condition with an ORDER BY on a partitioned table caused a server crash. (Bug#40494: http://bugs.mysql.com/40494) * Partitioning: Dropping or creating an index on a partitioned table managed by the InnoDB Plugin locked the table. (Bug#37453: http://bugs.mysql.com/37453) * Replication: Row-based replication failed with non-partitioned MyISAM tables having no indexes. (Bug#40004: http://bugs.mysql.com/40004) * With statement-based binary logging format and a transaction isolation level of READ COMMITTED or stricter, InnoDB printed an error because statement-based logging might lead to inconsistency between master and slave databases. However, this error was printed even when binary logging was not enabled (in which case, no such inconsistency can occur). (Bug#40360: http://bugs.mysql.com/40360) * The CHECK TABLE ... FOR UPGRADE statement did not check for incompatible collation changes made in MySQL 5.1.24. (This also affects mysqlcheck and mysql_upgrade, which cause that statement to be executed.) Prior to this fix, a binary upgrade (performed without dumping tables with mysqldump before the upgrade and reloading the dump file after the upgrade) would corrupt tables. After the fix, CHECK TABLE ... FOR UPGRADE properly detects the problem and upgrades tables. However, the fix is not backward compatible and can result in a downgrading problem under these circumstances: 1. Perform a binary upgrade to a version of MySQL that includes the fix. 2. Run CHECK TABLE ... FOR UPGRADE (or mysqlcheck or mysql_upgrade) to upgrade tables. 3. Perform a binary downgrade to a version of MySQL that does not include the fix. The solution is to dump tables with mysqldump before the downgrade and reload the dump file after the downgrade. Alternatively, drop and recreate affected indexes. (Bug#40053: http://bugs.mysql.com/40053) * Some recent releases for Solaris 10 were built on Solaris 10 U5, which included a new version of libnsl.so that does not work on U4 or earlier. To correct this, Solaris 10 builds now are created on machines that do not have that upgraded libnsl.so, so that they will work on Solaris 10 installations both with and without the upgraded libnsl.so. (Bug#39074: http://bugs.mysql.com/39074) * XA transaction rollbacks could result in corrupted transaction states and a server crash. (Bug#28323: http://bugs.mysql.com/28323) * ALTER TABLE for an ENUM column could change column values. (Bug#23113: http://bugs.mysql.com/23113) -- For a choice in the future of personal computing, Join VOICE - http://www.os2voice.org [Moderator's note: All posts are sent without guarantee to the accuracy of the content. We try to verify details and URLs but this is an entirely volunteer run list, so 100% fact checking and the quality/useability of products announced here is impossible. If you respond to this post please remove the DESPAM from the poster's email addresses. Please do not send requests for information about a specific post to the moderator unless it is an update or I sent it.] -- To unsubscribe yourself from this list, send the following message to majormajor at os2voice.org unsubscribe news your.email.address at here end Or, visit http://www.os2voice.org/MailingLists.php If you have an announcement you would like posted to the VOICE News list, please send it to submit at os2voice.org or go to http://www.os2voice.org/SubmitNews.php . Please include a valid reply address and a real contact name. If you wish to comment on this post, please reply to feedback at os2voice.org