The MariaDB project is pleased to announce the immediate availability of the MariaDB 5.5.31. 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.31
Release Notes Changelog What is MariaDB 5.5?
This release is primarily a bug-fix release.
Includes MariaDB 5.3.12 and MySQL 5.5.31
This release includes MariaDB 5.3.12 and MySQL 5.5.31.
Other Notable Updates
- Includes XtraDB from Percona Server-5.5.30-rel30.2
- Includes an alpha version of the QUERY_CACHE_INFO plugin, that allows to see the content of the query cache via the corresponding INFORMATION_SCHEMA table.
- MariaDB MSI packages for Windows include the latest HeidiSQL 8.0.
- Support for FusionIO/directFS atomic writes added (MDEV-4338). See the following for more information:
Ubuntu 8.04 LTS “Hardy” and 11.10 “Oneiric” Deprecated
In accordance with the MariaDB Deprecation Policy the following distributions have reached the end of their support periods (EOL):
- Ubuntu 8.04 LTS “Hardy”
- Ubuntu 11.10 “Oneiric”
- Mint 9 LTS “Isadora”
- Mint 12 “Lisa”
MariaDB 5.5.31) is therefore the last MariaDB release to feature packages for these distros. The repositories for them will remain online until the 5.5.32 release. At that time they will go away.
Thanks, and enjoy MariaDB!
The MariaDB project is pleased to announce the immediate availability of the MariaDB Java Client 1.1.2. 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 AskMonty Knowledgebase for general information about the client.
Download MariaDB Java Client 1.1.2
Release Notes Changelog About the MariaDB Java Client
Bugs fixed in this release
MariaDB Java Client 1.1.2 is a bug fix release. Some of the bugs fixed include the following:
PreparedStatement.getMetaData() will now return correct ResultSet metadata, also prior to statement execution. In this case, to retrieve metadata, statement will be prepared on the server side. (CONJ-21)
- Performance enhancement :
Connection.getAutoCommit() will not more issue not issue “
select @@autocommit” query anymore. This information is also available in on status flags sent with OK/EOF protocol packets. Also,
Connection.setAutoCommit() will be a no-op, if autocommit status is already the same as desired one (CONJ-30)
- Fixed several issues with CLOB datatype and
ResultSet.setCharacterStream() -non-ASCII character could get lost after
setCharacterStream(). CLOB was errneously sent to server as binary (using
_BINARY introducer). (CONJ-31)
- CHAR BINARY and VARCHAR BINARY were errnously handled as binary type. They are now correctly treated as CHAR/VARCHAR with binary collation. (CONJ-28)
Blob.getBinaryStream() could return blob with incorrect size (CONJ-31)
- Fix server version string for MariaDB Server 10.0.2 (CONJ-32)
Many developers use master-slave replication to solve a number of different problems, including problems with performance, supporting the backup of different databases, and as a part of a larger solution to alleviate system failures. Traditionally, master-slave replication is done with real servers, but it can also be done with cloud database servers. This guest post from Jelastic (originally published here) describes how to set up MariaDB master-slave replication using their Jelastic PaaS (Platform as a Service).