At OSCON, if you’re into the MySQL world, the day to be paying attention to BoFs is clearly Wednesday, 24 July 2013. We have a MariaDB BoF at D136 at 8pm-9pm, but before that you might be at the MySQL BoF in the same room, or you might be in Peter Zaitsev’s BoF on MySQL, NoSQL, Big Data – Better Together in E141. So figure out how to split yourself at 7-8pm, and once you’re done, come from 8-9pm at D136 on Wednesday and join the MariaDB crew at OSCON!
We’ll also be at the SkySQL booth, so come by Booth 815 and get some free t-shirts, stickers, or support the MariaDB community by being a foundation donor.
The MariaDB project is pleased to announce the immediate availability of MariaDB 5.5.32. 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.32
Release Notes Changelog What is MariaDB 5.5?
This release is primarily a bug-fix release.
This release includes MariaDB 5.3.12 and MySQL 5.5.32. See Changes in MySQL 5.5.32 for what changed in MySQL.
Other Notable Information
- Includes XtraDB from Percona Server-5.5.32-rel31.0
Thanks, and enjoy MariaDB!
The MariaDB project is pleased to announce the immediate availability of the MariaDB Java Client 1.1.3. 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.3
Release Notes Changelog About the MariaDB Java Client
- On Windows, it is now possible to use named pipes if server enables them. To connect to the server using named pipe, pass pipe=<pipe_name> URL parameter or property. The pipe filename name should be passed without the
\\pipe\<machine> prefix. (CONJ-36)
- It is now possible to do SSL validation for self signed certificates, using serverSslCert, (provide CA certificate for the server’s certificate). It allows to avoid SSL handshake errors (untrusted CA) when working with self-signed certificates, and is more secure than the existing trustServerCertificate option. (CONJ-48)
Bugs fixed in this release
Some of the bugs fixed include the following:
- Change assertion in
PacketOutputStream.startPacket() to be IOException, so it can be caught. “Last packet not finished” condition can happen , if underlying stream is broken (e.g write operation failed) (CONJ-34)
- If custom
SocketFactory creates an already connected socket, do not execute Socket.connect() (CONJ-37)
- Ensure proper locking in
MySQLCallableStatement.execute(), in scenarios that use single connection simultaneously from multiple threads. Hold the connection lock for the duration of 3 operations – setting parameters , executing statement, and reading off output parameters) (CONJ-38)
- For multi-row inserts,
getGeneratedKeys() will return ResultSet with multiple entries (CONJ-39)
java.util.Date can now be passed to PreparedStatement.setObject(). (CONJ-40)
- Allow for missing space it temporal escapes, for better compatibility with ConnectorJ (CONJ-42)
PreparedStatement.getResultSetMetaData() called before query execution threw exception, if query string contained at least once placeholder (CONJ-43)
DatabaseMetaData.getPrimaryKeys() returned incorrect value in KEY_SEQ column (CONJ-41)
- (Performance enhancement) Changed
DatabaseMetadata.getImportedKeys() not to use information schema, but to parse the output of “show create table” instead. This considerably speeds up several scenarios involving Hibernate (CONJ-35)
ResultSet.getDisplaySize() for character columns – due to UTF-8 usage it was 3x more than expected (size in bytes, instead of size in chars)
- Fix bug in prepared statement parsing code (skipping next character after backslash ‘\’)(CONJ-44)
Statement.executeBatch() methods to throw
BatchUpdateException, as in JDBC spec (CONJ-47)