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

12/20/2005
MySQL 5.0.17 released.

MySQL 5.0.17, a new GA/production 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 a bugfix release for the current production version.

If you are not aware of the changes introduced with version 5.0, please see the high-level description and pay special attention to the manual, section 2.10.2, "Upgrading from Version 4.1 to 5.0."

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

Changes in release 5.0.17:

Functionality added or changed:

  • The syntax for CREATE TRIGGER now includes a DEFINER clause for specifying which access privileges to check at trigger invocation time. See Section 18.1, "CREATE TRIGGER Syntax" for more information.
  • Added a DEFINER column to the INFORMATION_SCHEMA.TRIGGERS table.
  • Invoking a stored function or trigger creates a new savepoint level. When the function or trigger finishes, the previous savepoint level is restored.
  • Recursion is allowed in stored procedures. Recursive stored functions and triggers still are disallowed.

Bugs fixed:

  • NDB Cluster: Using ORDER BY primary_key_column when selecting from a table having the primary key on a VARCHAR column caused a forced shutdown of the cluster.
  • GROUP BY on a view column did not correctly account for the possibility that the column could contain NULL values.
  • Multiple-table update operations were counting updates and not updated rows. As a result, if a row had several updates it was counted several times for the "rows matched" value but updated only once.
  • Revised table locking to allow proper assessment of view security.
  • Within a stored procedure, inserting with INSERT ... SELECT into a table with an AUTO_INCREMENT column did not generate the correct sequence number.
  • SELECT queries that began with an opening parenthesis were not being placed in the query cache.
  • Space truncation was being ignored when inserting into BINARY or VARBINARY columns. Now space truncation results in a warning, or an error in strict mode.

And many more...

Source: dev.mysql.com

twitterfacebook