Skip navigation links

Additional languages
5.2.22 Changes in MySQL 5.0.41 (01 May 2007) »
Section Navigation      [Toggle]

5.2.21. Changes in MySQL 5.0.42 [MRU] (23 May 2007)

This is a Monthly Rapid Update release of the MySQL Enterprise Server 5.0.

Functionality added or changed:

  • Incompatible Change: Prior to this release, when DATE values were compared with DATETIME values, the time portion of the DATETIME value was ignored, or the comparison could be performed as a string compare. Now a DATE value is coerced to the DATETIME type by adding the time portion as 00:00:00. To mimic the old behavior, use the CAST() function as shown in this example: SELECT date_col = CAST(NOW() AS DATE) FROM table;. (Bug#28929)

  • Incompatible Change: INSERT DELAYED is now downgraded to a normal INSERT if the statement uses functions that access tables or triggers, or that is called from a function or a trigger.

    This was done to resolve the following interrelated issues:

    • The server could abort or deadlock for INSERT DELAYED statements for which another insert was performed implicitly (for example, via a stored function that inserted a row).

    • A trigger using an INSERT DELAYED caused the error INSERT DELAYED can't be used with table ... because it is locked with LOCK TABLES although the target table was not actually locked.

    • INSERT DELAYED into a table with a BEFORE INSERT or AFTER INSERT trigger gave an incorrect NEW pseudocolumn value and caused the server to deadlock or abort.

    (Bug#21483)

    See also Bug#20497, Bug#21714.

Bugs fixed:

  • Security Fix: Use of a view could allow a user to gain update privileges for tables in other databases. (Bug#27878, CVE-2007-3782)

  • Security Fix: The requirement of the DROP privilege for RENAME TABLE was not enforced. (Bug#27515, CVE-2007-2691)

  • Security Fix: If a stored routine was declared using SQL SECURITY INVOKER, a user who invoked the routine could gain privileges. (Bug#27337, CVE-2007-2692)