MariaDB Connector/J 2.0.0 Release Notes
Release date: 20 April 2017
MariaDB Connector/J 2.0.0-RC is a RC (Release candidate) release.
For an overview of MariaDB Connector/J see the About MariaDB Connector/J page
Java 8 is now minimum required version.
Handle CLIENT_DEPRECATE_EOF flag
handle SERVER_SESSION_STATE_CHANGE status flag
- driver does now always get current database, even when database is changed by query.
- when using rewriteBatchedStatements does return correct autoincrement ids even when session variable @auto_increment_increment has change during session.
improve setQueryTimeout to use SET STATEMENT max_statement_time
Previous implementation of query timeout handling (using Statement.setQueryTimeout) will create an additional thread with a scheduler.
When timeout is reached, a temporary connection will be created to permit executing "KILL QUERY <current connection id>", then closing the temporary connection.
When query ended before timeout, the scheduled task will be canceled.
If server is > 10.1.2, query timeout will be handle server side using "SET MAX_STATEMENT_TIME FOR" command.
Real cancelling Streaming result sets
When closing a Statement that was fetching a result-set (using Statement.setFetchSize) and all rows where not read at the time of closing, a kill query command will be executed on close, to avoid having to parse all remaining results.
Memory optimization : streaming query
Very big command now doesn't use any intermediate buffer. Commands are send directly to socket avoiding using memory, This permit to send very large object (1G) without using any additional memory.
Faster connection : bundle first commands in authentication packet Driver execute different command on connection. Those queries are now send using pipeline (all queries are send, then only all results are reads).
New Options :
|usePipelineAuth||Fast connection creation.Default: true. Since 2.0.0|
Performance improvement storing data in resultset
Parsing row result optimisation to avoid creating byte array to the maximum for faster results and less memory use.
Remaining JDBC 4.2 missing implementation :
- CONJ-414 - support for large update count [CONJ-414]
- CONJ-409 - PrepareStatement.setObject(...) support for with java 8 temporal temporal object.
- CONJ-411 - support for Statement maxFieldSize
- CONJ-443 - NullpointerException when making concurrent procedure calls
- CONJ-391 - Improve connection using SELECT in place of SHOW to avoid creating a mutex server side.
- CONJ-402 - tcpKeepAlive option now default to true.
- CONJ-448 - QueryException: Incorrect arguments to mysqld_stmt_execute on inserting an "emptyString"-Lob with JPA
- CONJ-451 - Respect type parameter of ResultSet.getObject with type
- CONJ-455 - MetaData : tinyInt1isBit doesn't work properly in TINYINT(1) column that is marked as UNSIGNED
- CONJ-450 - NPE on setClientInfo if value is an empty string
- CONJ-457 - trustStore : Retain leading slash when trust store beings with 'file:/'
- CONJ-160 - ConnectionPool test using hikariCP
- CONJ-307 - valid connector java 9 early access
- CONJ-402 - make tcpKeepAlive option default to true
- CONJ-411 - Implement Statement maxFieldSize
- CONJ-449 - Permit CallableStatement streaming
Be notified of new MariaDB Server releases automatically by subscribing to the MariaDB Foundation community announce 'at' mariadb.org announcement list (this is a low traffic, announce-only list). MariaDB Corporation customers will be notified for all new releases, security issues and critical bug fixes for all MariaDB Corporation products thanks to the Notification Services.
MariaDB may already be included in your favorite OS distribution. More information can be found on the Distributions which Include MariaDB page.