MariaDB 5.3.9 Changelog

Download |Release Notes |Changelog |Overview of 5.3

Release date: 02 Oct 2012

For the highlights of this release, see the release notes.

The revision number links will take you to the revision's page on Launchpad. On Launchpad you can view more details of the revision and view diffs of the code modified in that revision.

• Revision #3583 Mon 2012-10-01 15:42:49 +0200

  • increase the version

• Sat 2012-09-29 22:44:13 -0700

  • Fixed ().

  • In some rare cases when the value of the system variable join_buffer_size was set to a number less than 256 the function JOIN_CACHE::set_constants determined the size of an offset in the join buffer equal to 1 though the minimal join buffer required more than 256 bytes. This could cause a crash of the server when records from the join buffer were read.

• Fri 2012-09-28 09:54:43 +0200

  • Fix compiler warnings that breaks build (-Werror).

• [merge] Thu 2012-09-27 15:02:17 +0200

  • merge

  • [merge] Thu 2012-09-27 12:59:23 +0200

    • Merge from 5.1
• Thu 2012-09-27 13:18:07 +0500

  • backport --ignore-db-dir

  • The feature was backported from MySQL 5.6.

  • Some code was added to make commands as
• [merge] Mon 2012-09-24 17:29:26 +0200

  • merge

  • [merge] Mon 2012-09-24 13:57:45 +0200

    • merge
• Thu 2012-09-20 12:48:59 +0300

  • fix.

  • After pullout item during single row subselect transformation it should be fixed properly.

• [merge] Mon 2012-09-17 11:13:46 +0300

  • Merged the fix for , .

  • Performed some refactoring and simplification that was enabled and required by the merge.

  • Fri 2012-09-14 11:26:01 +0300
• Fri 2012-09-07 09:39:51 +0300

  • Fix of .

  • As far as we reopen tables so TABLE become invalid we should remove the pointer on cleanup().

• Wed 2012-09-05 23:23:58 +0300

  • fix.

  • Link view/derived table fields to a real table to check turning the table record to null row.

  • Item_direct_view_ref wrapper now checks if table is turned to null row.

• Fri 2012-08-31 19:50:45 +0500

  • st_distance() results are incorrect depending on variable order.

  • Autointersections of an object were treated as nodes, so the wrong result.

  • per-file comments:
• Fri 2012-08-31 12:01:52 +0200

  • compilation warning

• Thu 2012-08-30 10:53:49 +0200

  • : fdatasync() does not correctly flush growing binlog file.

  • When we append data to the binlog file, we use fdatasync() to ensure the data gets to disk so that crash recovery can work.

  • Unfortunately there seems to be a bug in ext3/ext4 on linux, so that fdatasync() does not correctly sync all data when the size of a file is increased. This causes crash recovery to not work correctly (it loses transactions from the binlog).

• Thu 2012-08-30 09:05:27 +0200

  • Microseconds: In time functions precision is calculated modulo 256

  • store the precision in uint, not uint8

• Wed 2012-08-29 18:36:57 +0200

  • Microseconds: Precision is ignored in CURRENT_TIMESTAMP(N) when it is given as a default column value

  • The syntax for specifying precision in the DEFAULT clause is unintentional and unsupported.

  • Don't allow it anymore.

• Wed 2012-08-29 17:55:59 +0200

  • Addition of a time interval reduces the resulting value

    1. Field_newdate::get_date should refuse to return a date with zeros when TIME_NO_ZERO_IN_DATE is set, not when TIME_FUZZY_DATE is unset

    2. Item_func_to_days and Item_date_add_interval can only work with valid dates, no zeros allowed.

• Wed 2012-08-29 10:59:51 +0200

  • An out-of-range datetime value (with a 5-digit year) can be created and cause troubles

    • fix Item_func_add_time::get_date() to generate valid dates.

    • Move the validity check inside get_date_from_daynr() instead of relying on callers
• Wed 2012-08-29 11:35:42 +0300

  • : fixed incorrect error check.

• Tue 2012-08-28 13:51:01 +0400

  • Fix bugs in BatchedKeyAccess that show up when working with a storage engine in HA_MRR_NO_ASSOCIATION mode.

  • (there is no testcase because we don't ship any such engines currently)