Author: MariaDB Foundation
-
MariaDB 10.0.2-alpha Now Available
The MariaDB project is pleased to announce the immediate availability of MariaDB 10.0.2. This is an alpha release. See the release notes and changelog for details.
Download MariaDB 10.0.2
Release Notes Changelog Overview of 10.0
APT and YUM Repository Configuration Generator
About this Release
MariaDB 10.0 is the development version of MariaDB. It is built on the MariaDB 5.5 series with backported features from MySQL 5.6 and entirely new features not found anywhere else.
This is the third 10.0-based release, and we are […]
-
MariaDB 5.5.30 now available
The MariaDB project is pleased to announce the immediate availability of MariaDB 5.5.30. This is a bug fix release. See the release notes and changelog for details.
Download MariaDB 5.5.30
Release Notes Changelog Overview of 5.5
APT and YUM Repository Configuration Generator
User Feedback plugin
MariaDB includes a User Feedback plugin. This plugin is disabled by default. If enabled, it submits basic, completely anonymous MariaDB usage information. This information is used by the developers to track trends in MariaDB usage to better guide […]
-
MariaDB Galera Cluster 5.5.29 Stable (GA) released
After some final testing and polishing, the MariaDB project and Codership are pleased to announce the release of MariaDB Galera Cluster 5.5.29. This is a Stable (GA) release. MariaDB Galera Cluster links:
-
MariaDB Java Client 1.1.1 Released
The MariaDB Java Client 1.1.1 has been released. You can download it here.
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.
New functionality in this release
- Implement tcpAbortiveClose option, for “hard” socket close (CONJ-27)
- This option can be used in environments where connections are created and closed in rapid succession. Often, it is not possible to create a socket in such environment after a while, since all local “ephemeral” ports are used up by TCP connections in TCP_WAIT state. Using tcpAbortiveClose works around this problem by resetting TCP connections rather (abortive or hard close) than doing an orderly close. It is accomplished by using socket.setSoLinger(true,0) for abortive close.
- Implement tcpAbortiveClose option, for “hard” socket close (CONJ-27)
-
MariaDB 5.5.29, 5.3.12, 5.2.14, 5.1.67 now available
The MariaDB project is pleased to announce the immediate availability of the following new stable (GA) MariaDB versions:
-
MariaDB Java Client 1.1.0 released
The MariaDB Java Client 1.1.0 has been released. You can download it here.
This version focused on fixing all known database metadata bugs and ConnnectorJ incompatibilities. Specific fixes include:
- Consistent, compatible with ConnectorJ handling of JDBC catalogs vs schemas vs databases
- Implementation of several missing methods in DatabaseMetaData
- Better handling of statement timeouts
- OSGi-specific entries have been added to MANIFEST.MF so it can be used in OSGi environments
- Added support for dumpQueriesOnException=true in the JDBC URL
- Added support for IPv6 addresses in the connector
- Added SSL support
- and more…
-
Announcing MariaDB 10.0.0 Alpha
The MariaDB project is pleased to announce the immediate availability of MariaDB 10.0.0! This is an alpha release.
MariaDB 10.0 is the current development version of MariaDB. It is built on the MariaDB 5.5 series with backported features from MySQL 5.6 and entirely new features not found anywhere else. See “Explanation on MariaDB 10.0” and “What comes in between MariaDB now and MySQL 5.6?” for more information on why we’re calling this series “MariaDB 10.0”.
This is the first 10.0-based […]
-
The Query Cache and Partitions
Like others we were not satisfied with the fix for a bug in MySQL which caused the query cache and partitioning to not work reliably together. The bug, in simple terms, was that if the query cache was enabled and you used partitioned tables and if a partitioned table was using a transactional engine like InnoDB or XtraDB, the query cache could, under certain circumstances, return incorrect results.
Returning incorrect results is a definite, high-priority bug. However, the upstream fix was to disable all caching of queries from […]