Download | Release Notes | Changelog |

Release date: 26 Sep 2017

MariaDB Connector/J 2.1.2 is a Stable (GA) release.

Bug

• [] Batch result-set return array correction when DELETE statement when bulk option is used

• [] better error message getting metadata information when SQL syntax is wrong

• [] Resultset.last() return wrong value if resultset has only one result

• [] Error executing LOAD DATA LOCAL INFILE when file is larger than max_allowed_packet

Misc

• ensuring Connection.isValid(timeout) always respect timeout value

Download | Release Notes | Changelog |

Release date: 6 Sep 2017

MariaDB Connector/J 2.1.1 is a Stable (GA) release.

Bug

• [] Updatable result-set possible NPE when same field is repeated.

• [] ResultSet method wasNull() always return true after a call on a "null-date" field binary protocol handling

• [] Permit using updatable result-set when fetching

• [] Add legacy SSL certificate Hostname verification with CN even when SAN are set

• [] Improve MariaDB driver stability in case JNA errors

Misc

• correct typo in error message when setting wrong parameter

• add trace to HostnameVerifier implementation

• handling connection error when no database is provided

Download | Release Notes | Changelog |

Release date: 31 July 2017

MariaDB Connector/J 2.1.0 is a Stable (GA) release.

Notable Changes

This version is a general availability (GA) release. (2.x version need java 8+)

Notable changes and additions

: verification of SSL Certificate Name Mismatch

When using ssl, driver check hostname against the server's identity as presented in the server's Certificate (checking alternative names or certificate CN) to prevent man-in-the-middle attack. Verification is disabled when the option "trustServerCertificate" is set.

A new option "disableSslHostnameVerification" permit to deactivate this validation.

- Galera validation

When configuration with multi-master, Connection.isValid() will not only validate connection, but host state (@@wsrep_cluster_status). A connection to a node that is not in primary mode will return false (meaning that in pool, connection will be discarded)

- ResultSet.update* methods implementation

ResultSet.update* methods aren't implemented statement using ResultSet.CONCUR_UPDATABLE are now able to update record. example:

- faster batch insert

Use dedicated protocol for batch insert when possible. (batch without Statement.RETURN_GENERATED_KEYS and streams) to have faster batch (significant only if server >= ).

A new option "useBulkStmts" permit to deactivate this functionality.

other evolution

• [] Connection.getCatalog() optimisation for 10.2+ server using new session_track_schema capabilities

• [] Failover handle automatic reconnection on KILL command

Bug

• [] isolation leak when using multiple pools on same VM on failover

• [] regression on aurora Connection Connection.isReadOnly()

• [] correcting issue that ended throwing "Unknown prepared statement handler given to mysqld_stmt_execute"

• [] return rounded numeric when querying on a decimal field in place of throwing an exception for compatibility