Documentation Home
MySQL Connector/J Release Notes
Related Documentation Download these Release Notes
PDF (US Ltr) - 362.7Kb
PDF (A4) - 361.4Kb


MySQL Connector/J Release Notes  /  Changes in MySQL Connector/J Version 8.x  /  Changes in MySQL Connector/J 8.2.0 (2023-10-25, General Availability)

Changes in MySQL Connector/J 8.2.0 (2023-10-25, General Availability)

Version 8.2.0 is a new GA release of MySQL Connector/J. MySQL Connector/J 8.2.0 supersedes 8.1 and is recommended for use on production systems. This release can be used against MySQL Server version 5.7 and later. It supports the Java Database Connectivity (JDBC) 4.2 API, and implements the X DevAPI.

Functionality Added or Changed

  • Added the missing implementation for Connection.releaseSavepoint(). (Bug #35811592)

  • Connector/J now supports WebAuthn Authentication. See Connecting Using Web Authentication (WebAuthn) Authentication for details. (WL #15197)

  • The auto-deserialization function for BLOB objects, deprecated since release 8.1.0, is now removed. (WL #15747)

Bugs Fixed

  • The SessionStateChanges objects failed to provide proper values for section state changes. This was because Connector/J parsed the OK_Packet incorrectly, and this patch fixes the issue. (Bug #35358417)

  • Using javax.sql.rowset.CachedRowSet#getDate() or javax.sql.rowset.CachedRowSet#getTimestamp() on DATETIME fields resulted in a ClassCastException. It was because the default return type of DATETIME fields by ResultSet.getObject() was java.time.LocalDateTime instead of java.sql.Timestamp. To prevent the exception, a new connection property, treatMysqlDatetimeAsTimestamp, now allows the return type of DATETIME by ResultSet.getObject() to be changed to java.sql.Timestamp. (Bug #107215, Bug #34139593)

  • Obtaining a connection from a MysqlConnectionPoolDataSource made Connector/J reset its connection state unless the connection property paranoid was set to be true. During the reset, the autocommit mode of the session was restored to the default value specified on the server by the system variable autocommit, while the JDBC specification mandates that autocommit be always enabled for a freshly created connection. With this patch, the connection reset will always enable autocommit in the situation. (Bug #91351, Bug #28225464)