EMS logo

Products Navigation

choose your database tool

Our Partnership Status

Microsoft Certified Partner
Oracle Certified Partner
Embarcadero Technology Partner

SQL Industry News

All SQL News

MySQL 5.1.7-beta released.

MySQL 5.1.7, a new version of the popular Open Source Database Management System, has been released. The Community Edition is now available in source and binary form for a number of platforms from our download pages and mirror sites.

Note that not all mirror sites may be up to date at this point in time - if you can't find this version on some mirror, please try again later or choose another download site.

This is the first published Beta release in the 5.1 series. All attention will continue to be focused on fixing bugs and stabilizing 5.1 for later production release.

NOTE: This Beta release, as any other pre-production release, should not be installed on ``production'' level systems or systems with critical data. It is good practice to back up your data before installing any new version of software. Although MySQL has worked very hard to ensure a high level of quality, protect your data by making a backup as you would for any software beta release.

Please refer to our bug database for more details about the individual bugs fixed in this version.

Changes in release 5.1.7:

Functionality added or changed:

  • Incompatible change: TYPE = engine_name is no longer accepted as a synonym for the ENGINE = engine_name table option. (TYPE has been deprecated for some time already.)
  • Added the mysql_upgrade program that checks all tables for incompatibilities with the current version of MySQL Server and repairs them if necessary. This program should be run for each MySQL upgrade (rather than mysql_fix_privilege_tables). See Section 5.5.2, "mysql_upgrade - Check Tables for MySQL Upgrade."
  • All subpartitions within a given partitioned table are now guaranteed to have unique names.
  • Added the FOR UPGRADE option for the CHECK TABLE statement. This option checks whether tables are incompatible with the current version of MySQL Server. Also added the --check-upgrade option to mysqlcheck that invokes CHECK TABLE with the FOR UPGRADE option. Added the --fix-db-names and --fix-table-names options to mysqlcheck.
  • Added the RENAME DATABASE statement. This is a first version with limited functionality, especially it does not migrate any stored routines or events to the new schema (stored routines and events must be redefined in the new database). Its current main purpose is for migration of old data that uses filenames/dirnames in some coding page to the new filename encoding. Like a RENAME TABLE, it will also not change any account privileges listed in the system tables (this needs to be done manually, if this is required for the renamed table).
  • The SQL mode in effect at the time an event is created or altered is recorded and used during event execution.
  • CREATE/DROP/ALTER EVENT statements are not allowed in triggers.