The Ultimate Guide to High Availability with MariaDB
This is a read-only copy of the MariaDB Knowledgebase generated on 2024-12-18. For the latest, interactive version please visit https://mariadb.com/kb/.

MariaDB 5.2.2 Changelog

Download | Release Notes | Changelog | Overview of 5.2

Release date: 28 Sep 2010

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 #2870:
    • Move maria_upgrade() out of maria_init() as in standalone programs maria_data_root is not set.
    • Fixed failing pbxt test
  • Revision #2869:
    • Rename control file and log files from maria_xxx to aria_xxx when upgrading from MariaDB 5.1
    • Fix cleanup to really remove 'aria_log' files. Fixes failures in maria unit tests on some platforms.
    • Fixed compiler warnings
  • Revision #2868:
    • fix the sphinx test suite to work when sphinxse is statically linked into the server
  • Revision #2867: [merge]
  • Revision #2866:
    • extended configure script to report plugin configuration summary.
    • corrected the manual url to point to kb
  • Revision #2865:
    • build windows binaries with federatedx, not federated.
  • Revision #2864:
    • make_win_bin_dist: include all dynamic plugins, not only innodb_plugin
  • Revision #2863: [merge]
    • merge with 5.1
  • Revision #2862:
    • fixes for make dist, 32-bit OS, and other buildbot failures
  • Revision #2861:
    • oqgraph and sphinx on windows
  • Revision #2860:
    • fix bad merge that broke make distcheck
  • Revision #2859:
    • MYSQL_PLUGIN_WITHOUT() macro for plug.in
    • Using it in oqgraph/plug.in to fix Bug #635633
  • Revision #2858:
    • provide maria* aliases for aria* command-line options, status and system variables
  • Revision #2857:
    • rename maria to aria
  • Revision #2856:
    • always run information_schema_all_engines without safemalloc (otherwise it often times out)
  • Revision #2855:
    • add sphinx suite
  • Revision #2854:
    • add suite.pm for oqgraph suite;fix suite.opt
  • Revision #2853:
    • build federared* with libmysqlservices
  • Revision #2852:
    • restore shifted error numbers
  • Revision #2851:
    • fix incorrect xtradb plugin metadata.
    • build innodb_plugin with *-all build scripts
  • Revision #2850: [merge]
    • merge with 5.1
  • Revision #2849:
    • Fixed compiler warnings
  • Revision #2848: [merge]
    • Automerge with 5.1
  • Revision #2847: [merge]
    • Automerge with 5.1
  • Revision #2846: [merge]
    • Merge with 5.1
  • Revision #2845: [merge]
    • Merge with 5.1 to get in critical bug fix that caused Aria tests to fail
  • Revision #2844: [merge]
    • Automatic merge
  • Revision #2843:
    • Fix of soft group commit (assigned LSN instead of file number). Found by Monty.
  • Revision #2842: [merge]
    • Merge with 5.1 to get bug fix for Bug #613408 Memory corruption with (M)aria storage engine and virtual columns
    • Fixed test case to test for virtual columns
  • Revision #2841:
    • Added extra argument to longlong2str() to make it have same prototype is int2str()
    • Changed to use longlong10_to_str() instead of longlong2str() when base is 10 or -10 as former is much faster than later
    • Changed my_vsnprintf() to use longlong2str instead of int2str() to get rid of warnings and to get support for long pointers even when long is 32 bit.
  • Revision #2840: [merge]
  • Revision #2839: [merge]
    • Merge with 5.1
  • Revision #2838:
    • Fixed compiler warnings and test failures
  • Revision #2837: [merge]
    • Merge with MariaDB 5.1.49
    • Removed references to HA_END_SPACE_KEY (which has been 0 for a long time)
  • Revision #2836:
    • Check of maria engine presence added.
    • Comment fixed.
  • Revision #2835:
    • Fix for Bug #612894
    • Support of virtual columns added to maria engine.
  • Revision #2834:
    • Fixed Bug #610890.
    • The CREATE SHOW TABLE command misplaced virtual column specifiers:
      • the AS clause for a virtual column was put before optional
      • character set attributes, not after them as required by the syntax.
  • Revision #2833: [merge]
    • Merge
    • Revision #2826.3.1:
      • Fixed Bug #607177.
      • Due to an invalid check for NULL of the second argument of the Item_func_round items performed in the code of Item_func_round::real_op the function ROUND sometimes could return wrong results.
  • Revision #2832: [merge]
  • Revision #2831: [merge]
    • Merge
    • none Fixed Bug #607168.
    • The command CREATE TABLE AS SELECT erroneously preserved the virtual properties of the virtual fields from the select list.
  • Revision #2830: [merge]
    • Merge
    • Revision #2826.1.1:
      • Fixed Bug #607566.
      • For queries with order by clauses that employed filesort usage of virtual column references in select lists could trigger assertion failures. It happened because a wrong vcol_set bitmap was used for filesort. It turned out that filesort required its own vcol_set bitmap.
      • Made management of the vcol_set bitmaps similar to the management of the read_set and write_set bitmaps.
  • Revision #2829:
  • Revision #2828:
    • Fixed compiler and valgrind warnings
  • Revision #2827:
    • Changed usage statistics to use 64 bit ints instead of 32 for all relevant variables.
    • Fixes Bug #583314 user_statistics - INT overflow
  • Revision #2826: [merge]
    • Merge
    • Revision #2822.2.1:
      • Fixed Bug #604503.
      • If the expression for a virtual column of table contained datetime comparison then the execution of the second query that used this virtual column caused a crash. It happened because the execution of the first query that used this virtual column inserted a cached item into the expression tree. The cached tree was allocated in the statement memory while the expression tree was allocated in the table memory.
      • Now the cached items that are inserted into expressions for virtual columns with datetime comparisons are always allocated in the same mem_root as the expressions for virtual columns. So now the inserted cached items are valid for any queries that use these virtual columns.
  • Revision #2825: [merge]
  • Revision #2824: [merge]
    • Merge patch for ha_rnd_init()
    • Revision #2822.1.1:
      • Fix for Bug #588251: doStartTableScan() result not checked.
      • The issue was that we didn't always check result of ha_rnd_init() which caused a problem for handlers that returned an error in this code.
        • Changed prototype of ha_rnd_init() to ensure that we get a compile warning if result is not checked.
        • Added ha_rnd_init_with_error() that prints error on failure.
        • Checked all usage of ha_rnd_init() and ensure we generate an error message on failures.
        • Changed init_read_record() to return 1 on failure.
  • Revision #2823:
    • Fixed Bug #603186.
    • There were two problems that caused wrong results reported with this bug.
      1. In some cases stored(persistent) virtual columns were not marked in the write_set and in the vcol_set bitmaps.
      2. If the list of fields in an insert command was empty then the values of the stored virtual columns were set to default.
    • To fix the first problem the function st_table::mark_virtual_columns_for_write was modified. Now the function has a parameter that says whether the virtual columns are to be marked for insert or for update.
    • To fix the second problem a special handling of empty insert lists is added in the function fill_record().
  • Revision #2822:
    • Fixed Bug #603654.
    • If a virtual column was used in the ORDER BY clause of a query and some of the columns this virtual column was based upon were not referenced anywhere in the query then the execution of the query could cause an assertion failure.
    • It happened because in this case the bitmap of the columns used for ordering keys was not formed correctly.
  • Revision #2821:
    • Fixed Bug #604549.
    • There was no error thrown when creating a table with a virtual table computed by an expression returning a row.
    • This caused a crash when inserting into the table.
    • Removed periods at the end of the error messages for virtual columns.
    • Adjusted output in test result files accordingly.
  • Revision #2820:
    • Initial import of SpinxSE, with fixes for MariaDB.
  • Revision #2819: [merge]
  • Revision #2818:
    • Fixed Bug #601164.
    • The functions mysql_delete and mysql_update lacked calls of updated_virtual_fields(). This caused wrong results for some DELETEs/UPDATEs.
    • Added test cases for this bug.
  • Revision #2817:
    • Make MariaDB compile with VS 2010
    • Most of the changes are backports from MySQL 5.5. Please note that the 64-bit build fails with VS 2010 and the 32-bit build has problems running mysql-test-run.pl.
    • Added files for compiling with VS 2010 and added them to Makefile.am.
    • ifdef'ed ETIMEDOUT, because it is defined by VS 2010 now
    • Removed not needed /MAP's from cmake files
Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.