Bugs Fixed

• Fixed incorrect type definitions in DatabaseMetaData.getTypeInfo() (CONJ-1234)

• Resolved potential race condition that could cause NullPointerException (CONJ-1247)

• avoids redundant queries for CallableStatement.getParameterMetaData() (CONJ-1250)

• Fixed SSL configuration issue where zero SSL settings only functioned without explicit SSL configuration ()

• Resolved GSSAPI authentication error when server exchanges begin with 0x01 byte ()

• Corrected DatabaseMetadata.getTypeInfo() returning incorrect values for AUTO_INCREMENT, FIXED_PREC_SCALE, and CASE_SENSITIVE fields ()

• Fixed getString method on BIT(1) fields to properly honor transformedBitIsBoolean configuration ()

• Enhanced metadata compatibility with MariaDB version 12.0 ()

• Improved performance of DatabaseMetaData.getExportedKeys method ()

  • Added new option

• Fixed issue to ensure correct catalog name is returned ()

Changelog

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

Bugs Fixed

• CONJ-1228 The method result-set.getObject(val) for a field of type BLOB returns an object of type Blob by default instead of the expected object of type byte[].

  • The following methods are not affected

    • resultset.getBytes(val)

    • resultset.getBlob(val)

    • resultset.getObject(val, byte[].class)

    • resultset.getObject(val, Blob.class) all returns expected type)

• System throws an SQLTimeoutException prematurely without checking all available connections

• DatabaseMetadata.getTypeInfo() is missing the data types UUID and VECTOR

• Incorrect behavior where XA connections are closed when regular connections are terminated - this is against JDBC specifications

• When using the parameter trustCertificateKeyStorePassword, alias for trustStorePassword, an exception is thrown

• The connection option disconnectOnExpiredPasswords was not handled by the connector..It controls the client behavior when connecting with an expired password.

  • When set to true (default), the client disconnects if it detects an expired password.

  • When false, the client maintains the connection and allows setting a new password.

Changelog

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

Support of the PARSEC Authentication Plugin which is provided starting with MariaDB Server 11.6. See 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

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

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:

Resultset:

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

• Batch import fails with exception "Unknown command"

• 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.

Support of the PARSEC Authentication Plugin which is provided starting with MariaDB Server 11.6. See 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.

While initially documented in 3.5.0, this feature was not in the released version.

New High Availability Mode With Loadbalancing For Reads - CONJ-1207

When running a multi-master cluster (i.e. MariaDB Cluster with Galera), writing to more than one node can lead to optimistic locking errors ("deadlocks") in some use cases. Writing concurrently to multiple nodes also doesn't result in performance improvements, due to having to synchronously replicate to all nodes. The new high availability mode “Load-balance-read” permits the use of masters in a failover manner (try first master, the next one if the first master fails) while distributing the load on replicas.

Example of connection string:

Equivalent of:

In the example the hosts 127.0.0.5, 127.0.0.6 will be used for writes, in a failover manner. 127.0.0.6,127.0.0.7 are of type replica, read load balancing will be used.

Permit bulk for INSERT ON DUPLICATE KEY UPDATE commands for 11.5.1+ servers - CONJ-1208

Since MDEV-30366, the server can return appropriate detailed answers. This was implemented, but not for specific INSERT ON DUPLICATE KEY UPDATE commands.

Bugs Fixed

• CONJ-1053 waffle-jna dependency is not declared optional in the module description

• CONJ-1196 setObject on java.util.Date is en/decode as java.sql.Date and truncates hour/minutes/seconds/ms while it must be en/decode like a java.sql.Timestamp

• CONJ-1211 JDBC 4.3 enquoteIdentifier missing validation

  • An identifier containing only number must be quoted, even if alwaysQuote parameter is set to false

  • Length validation must be done (< 64 characters).

• SQL commands ending with semicolon and trailing space are not using bulk

Changelog

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

_{This page is: Copyright © 2025 MariaDB. All rights reserved.}

_{This page is: Copyright © 2025 MariaDB. All rights reserved.}

_{This page is: Copyright © 2025 MariaDB. All rights reserved.}

_{This page is: Copyright © 2025 MariaDB. All rights reserved.}

_{This page is: Copyright © 2025 MariaDB. All rights reserved.}

_{This page is: Copyright © 2025 MariaDB. All rights reserved.}

_{This page is: Copyright © 2025 MariaDB. All rights reserved.}

_{This page is: Copyright © 2025 MariaDB. All rights reserved.}