Tag: MariaDB Java Client
-
MariaDB Java Client 1.1.8 now available
Download MariaDB Java Client 1.1.8
Release Notes Changelog About the MariaDB Java Client
The MariaDB project is pleased to announce the immediate availability of the MariaDB Java Client 1.1.8. 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 MariaDB Java Client.
Thanks, and enjoy MariaDB!
-
MariaDB Release Roundup, Feb 2014
The MariaDB developers have made several releases in the past week. Rather than post about all of them separately, we decided to combine them into one post. Details for each release are available on their individual Release Notes and Changelog pages.
MariaDB 5.5.36
First up is MariaDB 5.5.36. This is a Stable (GA) release. Apart from general maintenance, bug fixes, and updates, TokuDB is now included in RPM packages for CentOS 6 on x86-64.
Download MariaDB 5.5.36
Release Notes Changelog […]
-
MariaDB Java Client 1.1.4 Released
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
New functionality
It is now possible to connect to the server via Unix domain […]
-
MariaDB Java Client 1.1.3 Released
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
New functionality
- 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)
- 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
-
On performance of JDBC drivers.
Back when the first version of the MariaDB Java Client was released, someone asked in the comments about the performance characteristics of the driver compared to ConnectorJ. I answered with hand-waving, saying that nobody does anything stupid, the performance of the drivers would be roughly the same, but I promised to measure it and tell the world one day. And now that day has come. The day where three MySQL JDBC drivers (ConnectorJ, MariaDB JDBC, and Drizzle JDBC) are compared […]
-
MariaDB Java Client 1.1.2 Released
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 […]
-
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 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…