The Ultimate Guide to High Availability with MariaDB
This is a read-only copy of the MariaDB Knowledgebase generated on 2024-12-18. For the latest, interactive version please visit https://mariadb.com/kb/.

MariaDB Connector/J 3.3.2 Release Notes

The most recent Stable (GA) release of MariaDB Connector/J is:
MariaDB Connector/J 3.5.1

Download Release Notes Changelog Connector/J Overview

Release date: 19 Dec 2023

MariaDB Connector/J 3.3.2 is a Stable (GA) release, and will replace 3.2 as the maintenance releases.

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

Bugs Fixed

  • CONJ-1117 new option `returnMultiValuesGeneratedIds` for connector 2.x compatibility, so getGeneratedKeys() return all ids of multi-value inserts
  • CONJ-1140 regression caussing ClassCastException on DatabaseMetaData when use with option defaultFetchSize set
  • CONJ-1129 Metadata.getPrimaryKeys table comparison using like in place of strict equality
  • CONJ-1130 ensuring batch parameter are cleared after SQL Failure
  • CONJ-1131 NullPointerException when Calling getGeneratedKeys() after an SQL Failure
  • CONJ-1132 Ensuring reseting result for getUpdateCount() after an SQL Failure
  • CONJ-1135 ensuring BULK command not used when using INSERT ON DUPLICATE KEY UPDATE in order to always have unique affected rows by default
  • CONJ-1136 wrong decoding for Resultset.getByte() results for binary varchar fields
  • CONJ-1137 ensuring never having NPE in OkPacket when setting auto commit
  • CONJ-1138 Inconsistency in Behavior of PreparedStatement After closeOnCompletion() Between MariaDB and MySQL Connectors
  • CONJ-1049 Metadata getTableTypes result was not ordered by TABLE_TYPE

Changelog

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

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.