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)
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.
Bugs fixed in this release
- MySQLStatement will now indicate there are no more results by returning -1 from getUpdateCount() and null from getResultSet(),as mandated by the standard (CONJ-14)
- Introduced nullCatalogMeansCurrent parameter for compatibly with ConnectorJ, and make it default (CONJ-16)
- Prior to this change, DatabaseMetadata.getTables() or other methods of DatabaseMetaData that accept catalog names and return result sets would treat null as prescribed by the JDBC standard (null means no restriction which catalog is used). This behavior is now changed for the sake of compatibility. Starting with 1.1.1 , null for catalog name will mean current catalog. To get JDBC standard behavior, one needs to set nullCatalogMeansCurrent=false.
- DatabaseMedataData.getColumns() returned incorrect values in the “COLUMN_SIZE” column for character data.(CONJ-15))
- Prior to the change, octet size was returned (length in bytes). Depending on the character set used, it could be 3 times bigger than the length in characters that was specified by CREATE or ALTER table. This behavior is corrected in 1.1.1
- DatabaseMetaData.getColumns() always handled MySQL YEAR datatype as SMALLINT. (CONJ-19)
- The behavior is now fixed and getColumns returns either DATE or SMALLINT depending on how the ‘yearIsDateType’ parameter is set.
- ResultSetMetaData.getColumnName() returned an empty string in special cases (CONJ-17)
- ResultSetMetaData.getColumnName() returned and empty string for “non-columns” in a result set (functions, aggregates like count(*), and so on). The fix is to return the column label to be returned if the column name is empty.
- Ensure that getObject() returns byte array for CHAR BINARY.(CONJ-20)
- Also make sure that getColumnType(),getColumnClassName(),getColumnTypeName() return values indicate BINARY for fixed binary type.
- JVM does not exit if statement timeout is used.(CONJ-23)
- Constructor for Timer was corrected to ensure that the Timer thread has type background thread. Thus Timer won’t prevent JVM from exiting.
- Calling first() on “streaming” result set and using the result set afterwards generated NullPointerException (CONJ-24)
- Now a SQLException is thrown early on, in the first() call, since streaming results sets are not scrollable.
- Connection.close() hangs if there is an open streaming result set, and next() was not called on this result set (CONJ-25)
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…
See the Release Notes and Changelog for more information.
See also the About the MariaDB Java Client page in the AskMonty Knowledgebase.