MariaDB Connector/J 2.0.1 is a Stable(GA) release.
For an overview of MariaDB Connector/J see thepage
Notable Changes
Java 8 is the minimum required version
The last release with Java 7 compatibility is
Change from 2.0.1
The "useServerPrepStmts" option now defaults to false.
Benchmarks show that if the query has already been used (then prepared), there is a significant performance increase. On the other hand, when the command is not already prepared, the additional exchange for preparing this command will slightly slow down the overall execution of the command
prepare_bench
The applications that repeatedly use the same queries have the ability to activate this option, but the general case is to use the direct command (text protocol).
Binary protocol is permissive and did permit using character for LIMIT that accept only integer :
With the "useServerPrepStmts" set to false, LIMIT parameter must be set to numeric field:
- changing database metadata compatibility to 4.2
- Query that contain multiqueries with fetch and EOF deprecation failed
- Using of "slowQueryThresholdNanos" option with value > Integer.MAX_VALUE results in class cast exception
New Option : - new option "enablePacketDebug"
Implement some protocol changes that permit saving some bytes.
(part of ).
With a or MySQL 5.7 server, ensure driver state:
driver now always gets the current database, even when the database is changed by a query.
when using rewriteBatchedStatements, return the correct autoincrement ids even when the session variable @auto_increment_increment has changed during the session.
The 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 ", then closing the temporary connection.
When the query ends before timeout, the scheduled task will be canceled.
For servers > , the query timeout will be handled server side using the "SET MAX_STATEMENT_TIME FOR" command.
When closing a statement that was fetching a result-set (using Statement.setFetchSize) and all rows were not read at the time of closing, a kill query command will be executed on close, to avoid having to parse all remaining results.
Very large commands now don't use an intermediate buffer. Commands are sent directly to socket avoiding using memory. This permits sending very large objects (1G) without using any additional memory.
Faster connection: bundle first commands in authentication packet
The driver executes different commands on connection. Those queries are now sent using pipeline (all queries are sent, only then are all results read).
New Options:
Parsing row result optimisation to avoid creating byte array to the maximum for faster results and less memory use.
- support for large update count []
- PrepareStatement.setObject(...) support for with java 8 temporal object.
- support for Statement maxFieldSize
- NullpointerException when making concurrent procedure calls
- Improve connection using SELECT in place of SHOW to avoid creating a mutex server side.
