EMS logo

Products Navigation

choose your database tool

Our Partnership Status

Microsoft Certified Partner
Oracle Certified Partner
Embarcadero Technology Partner

SQL Industry News

MySQL News

MySQL 5.0.10-beta released.

A new version of MySQL Community Edition 5.0.10-beta Open Source database management system has been released. This version now includes support for Stored Procedures, Triggers, Views and many other features. It is now available in source and binary form for a number of platforms from our download pages at http://dev.mysql.com/downloads/ and mirror sites.

Note that not all mirror sites may be up-to-date at this point. If you cannot find this version on a particular mirror, please try again later or choose another download site.

This is the sixth Beta release in the 5.0 series. All attention will continue to be focused on fixing bugs and stabilizing 5.0 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 done its best 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 the bug database at http://bugs.mysql.com/ for more details about the individual open and resolved bugs in this version.

Changes in release 5.0.10:

Functionality added or changed:

  • Security improvement: Applied a patch that addresses a zlib data vulnerability that could result in a buffer overflow and code execution.
  • The viewing of triggers and trigger metadata has been enhanced as follows:
    • An extension to the SHOW command has been added: SHOW TRIGGERS can be used to view a listing of triggers. See Section, "SHOW TRIGGERS Syntax" for details.
    • The INFORMATION_SCHEMA database now includes a TRIGGERS table. See Section 22.1.16, "The INFORMATION_SCHEMA TRIGGERS Table" for details.
  • It is no longer necessary to issue an explicit LOCK TABLES for any tables accessed by a trigger prior to executing any statements that might invoke the trigger.
  • The namespace for triggers has changed. Previously, trigger names had to be unique per table. Now they must be unique within the schema (database). An implication of this change is that DROP TRIGGER syntax now uses a schema name instead of a table name (schema name is optional and, if omitted, the current schema will be used).
    Note: When upgrading from a previous version of MySQL 5 to MySQL 5.0.10 or newer, you must drop all triggers before upgrading and re-create them after or DROP TRIGGER will not work after the upgrade.

And many more...

Source: dev.mysql.com