This is a read-only copy of the MariaDB Knowledgebase generated on 2024-11-21. For the latest, interactive version please visit https://mariadb.com/kb/.

MariaDB 5.2.2 Release Notes

The most recent release in the MariaDB 5.2 series is: MariaDB 5.2.14

Download | Release Notes | Changelog | Overview of 5.2

Release date: 28 Sep 2010

This is a gamma release. In general this means we believe the code is ready for general usage (based on bug inflow), but we want more testing before calling it stable. For a list of every change made in this release, see the Changelog. For a description of this release see the MariaDB 5.1 overview.

In most respects MariaDB will work exactly as MySQL: all commands, interfaces, libraries and APIs that exist in MySQL also exist in MariaDB.

In addition to the differences noted in previous release notes and changelogs, the main new things in this version of MariaDB 5.2 are:

Includes MariaDB 5.1.50

For MariaDB 5.2.2 we have merged in all of the changes from MariaDB 5.1, which included MariaDB 5.1.50 + some new bug fixes which will be in MariaDB 5.1.51, and MySQL 5.1.51. The MariaDB 5.1.50 release notes have details of what changes were made.

Maria Storage Engine Renamed to Aria

In this version of MariaDB 5.2 the Maria Storage Engine has been renamed to Aria.

SphinxSE

The Sphinx Storage Engine has been added to MariaDB. It is built as a dynamically loadable .so plugin, so use it you need to perform a one-time INSTALL PLUGIN. See the SphinxSE page for more details.

Bug Fixes

The main drive for this version of MariaDB 5.2 (compared to the previous two beta releases) was to fix bugs and otherwise prepare for a stable release of MariaDB 5.2. So, as in previous releases, in MariaDB 5.2.2 many bug fixes and other improvements were made. See the Changelog for details and links to the bugs that were fixed.

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.