MariaDB Connector/J 3.5.0 Release Notes

Download Release Notes Changelog Connector/J Overview

Release date: 24 Oct 2024

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

For an overview of MariaDB Connector/J see the About MariaDB Connector/J page

The MariaDB Connector/J 3.5 release series is replacing the maintenance releases for the 3.4 release series, as the new release series is fully compatible with 3.4.

Notable changes

PARSEC Authentication - CONJ-1193

Support of the PARSEC Authentication Plugin which is provided starting with MariaDB Server 11.6. See parsec documentation for more details.

This requires java 15+ (to use java native ed25519 Algorithm implementation). For previous versions of java, this will require adding BouncyCastle as dependency.

New options `truststore`, `trustStorePassword` and `trustStoreType` - CONJ-1183

Those options permit the use of a specific truststore that differs from the Java default truststore. This has been added for MariaDB 2.x and MySQL connector compatibility. See documentation

New option `connectionCollation` - CONJ-1199

The Connector is using the utf8mb4 charset per default when establishing a connection. ‘connectionCollation’ can be used to define which utf8mb4 collation should be used. If not set the server default collation for utf8mb4 will be used.

Starting with MariaDB 11.4 we recommend to instead set character_set_collations

Support for methods setObject/getObject and setArray/getArray - CONJ-1205

This addition is a preparation for the Vector support of MariaDB Server

Example of Array:

Array valArray = connection.createArrayOf("float", new float[] {1, 2, 3});
try (PreparedStatement prep =
   connection.prepareStatement("INSERT INTO BinaryCodec(t0, t1) VALUES (?, ?, ?)")) {
 prep.setInt(1, 1);
 prep.setArray(2, valArray);
 prep.setObject(3, new float[] {4, 5, 6});
 prep.execute();
}

Resultset:

Array resArray = rs.getArray(2);
float[] res = rs.getObject(2, float[].class);

Bugs Fixed

  • CONJ-1202 A change of the collation via a session variable might be ignored
  • CONJ-1201 Incorrect default behavior for forceConnectionTimeZoneToSession
    • NOTE: If client and server use different time zones and no timezone options where used, MariaDB Connector/J 3.4 introduces a change which is forcing client timezone to the session. This behavior is an not intended incompatibility change compared to MariaDB Connector/J 3.3, which is corrected in MariaDB Connector/J 3.5 with this change
  • CONJ-1200 Batch import fails with exception "Unknown command"
  • CONJ-1187 Throw exception type SQLTimeoutException instead of SQLNonTransientConnectionException for connection timeouts

Changelog

For a complete list of changes made in MariaDB Connector/J 3.5.0, with links to detailed information on each push, see the changelog.

Comments

Comments loading...
Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.