The MariaDB project is pleased to announce the immediate availability of MariaDB 5.5.33a. This is a Stable (GA) release. See the Release Notes and Changelog for detailed information on this release and the What is MariaDB 5.5? page in the AskMonty Knowledgebase for general information about the MariaDB 5.5 series.
Download MariaDB 5.5.33a
Release Notes Changelog What is MariaDB 5.5?
This is a special bug-fix release for some packaging and other errors in the recent MariaDB 5.5.33 release.
Specific bugs fixed in this release include:
- MDEV-5035 Debian package conflict libmariadbclient18 vs. mariadb-server-5.3
- MDEV-5026 Cannot use system jemalloc
- MDEV-5015 Wrong result with an aggregate function, index and impossible condition inside OR
- MDEV-5029 Crash in MariaDB 5.5.33 with inconsistent .frm from older MariaDB release
Full details on these and other fixes are available in the changelog.
Debian and Ubuntu packaging fixes
There were issues with the
.deb packages in the 5.5.33 release. Before updating with
apt-get, check to make sure the mirror you are using has version 5.5.33a (not 5.5.33). To check, run the following commands:
sudo apt-get update
apt-cache show mariadb-server | grep Version
The output will look similar to this (raring will be replaced with whatever version of Ubuntu or Debian you are using):
user@host:~$ apt-cache show mariadb-server | grep Version
We’ve created a page for those who ran into the packaging bugs present in 5.5.33. It has instructions on how to get MariaDB back into a state where it can be upgraded successfully.
Thanks, and enjoy MariaDB!
The MariaDB project is pleased to announce the immediate availability of MariaDB 5.5.33. This is a Stable (GA) release. See the Release Notes and Changelog for detailed information on this release and the What is MariaDB 5.5? page in the AskMonty Knowledgebase for general information about the MariaDB 5.5 series.
Download MariaDB 5.5.33
Release Notes Changelog What is MariaDB 5.5?
Includes TokuDB Storage Engine
With this release of MariaDB we are pleased to announce the addition of the TokuDB storage engine from Tokutek. It is only available for the following distributions:
- Ubuntu 13.04 “Raring” 64-bit
- Ubuntu 12.10 “Quantal” 64-bit
- Debian 7 “Wheezy” 64-bit
- Fedora 18 64-bit
- Fedora 17 64-bit
The TokuDB package is available in the repositories of the above distributions. See How to Enable TokuDB in MariaDB for instructions on installing the package and enabling TokuDB.
The version of TokuDB included with MariaDB is different from the version from Tokutek. See the TokuDB Differences page for details.
Includes MySQL 5.5.33 and XtraDB 5.5.33
This release includes MySQL 5.5.33. See Changes in MySQL 5.5.33 for what changed in MySQL.
Also included is XtraDB from Percona Server 5.5.33-rel31.1
Other Notable Information
- MariaDB is now built with jemalloc by default on Linux (not on Solaris or Windows).
The MariaDB project is pleased to announce the immediate availability of the MariaDB Java Client 1.1.4. This is a Stable (GA) release. See the Release Notes and Changelog for detailed information on this release and the About the MariaDB Java Client page in the MariaDB Knowledge Base for general information about the client.
Download MariaDB Java Client 1.1.4
Release Notes Changelog About the MariaDB Java Client
It is now possible to connect to the server via Unix domain sockets (on Unix platforms) or shared memory (Windows). For domain socket connections, add “
localSocket=<socket_path>” to the connection URL. For shared memory connections, add “
Shared memory and unix domain socket support is implemented using Java Native Access (JNA) library, and this means that applications that use these features will need jna.jar and jna-platform.jar to be present in the classpath at runtime (CONJ-50, CONJ-51). More information about the JNA project can be found at https://github.com/twall/jna
Bugs fixed in this release
Some of the bugs fixed include:
ResultSet.getTimestamp() did not work with TIME columns (CONJ-54)
DatabaseMetaData will now return correct information about case senstivity handling, dependent on
lower_case_table_names database parameter(CONJ-55)
supportsMixedCaseIdentifiers(),supportsMixedCaseQuotedIdentifiers() will return true if
lower_case_table_names is 0 (case-sensitive)
storesLowerCaseIdentifiers(),storesLowerCaseQuotedIdentifiers() will return true if
lower_case_table_names is 1 ( case-insensitive, lowercase conversion)
storesMixedCase[Identifiers(),storesMixedCaseQuotedIdentifiers() will returns true if
lower_case_table_names is 2 (case-insensitive, but case-preserving)
DatabaseMetaData.getDatabaseMinorVersion() incorrectly returned major version instead of minor (CONJ-56)
PreparedStatement.setObject() now correctly handles objects of type
- If connection is idle,
Statement.cancel() is now a no-op. Previously, “KILL QUERY” was sent to database no matter whether statement was executed or not (CONJ-58)
- Provide public method
Driver.unloadDriver() to cleanup after driver unload, to workaround Tomcat’s classloading issues (CONJ-61)
PreparedStatement.toString() output more meaningful (CONJ-62)
The MariaDB Java Client can be used with MariaDB, MySQL, and Percona Server.