Version 9.3.0 is a new GA release of MySQL Connector/J. MySQL Connector/J 9.3.0 supersedes 9.2 and is recommended for use on production systems. This release can be used against MySQL Server version 8.0 and later. It supports the Java Database Connectivity (JDBC) 4.2 API, and implements the X DevAPI.
Starting from this release, when using the
authentication_kerberos_client
andauthentication_ldap_sasl_client
plugins for authentication, if you are using a JAAS login configuration file (which is optional), the onlyLoginModule
that Connector/J accepts iscom.sun.security.auth.module.Krb5LoginModule
. (Bug #37311996)Implementations of the
DatabaseMetaData
methods have been revised in order to refactor code, increase performance, and prevent potential problems with quotes in identifiers. (WL #16723)-
A number of methods that were missing from the
DatabaseMetaDataUsingInfoSchema
class have now been implemented:getBestRowIdentifier()
getCatalogs()
getSchemas()
getSchemas()
getTablePrivileges()
They are similar to their counterparts in the
DatabaseMetaData
class, but they query theINFORMATION_SCHEMA
for the information they provide. (WL #16756)
Some update methods in
UpdatableResultSet
did not check the validity of the cursor position used, resulting in aNullPointerException
when the cursor position was invalid. This patch puts in proper checks so that a proper exception is thrown instead in such situations. (Bug #20802830)When using a
CallableStatement
to execute a stored procedure, aMySQLSyntaxErrorException
was thrown if any parameter names contained an escaped character. (Bug #20279671)Calling
get
methods forCallableStatements
resulted occasionally inArrayIndexOutOfBoundsExceptions
due to mismatches between the placeholder indexes and parameter indexes. (Bug #19857207)Connector/J failed to validate properly the index parameter of the
get
methods forCallableStatements
, so that an improper index value was not caught when the methods were called, resulting inArrayIndexOutOfBoundsExceptions
. (Bug #19829452)UpdatableResultSet
did not map correctly and set the values for primary keys when refreshing rows, resulting increateSQLExceptions
. (Bug #117294, Bug #37523180)The matching of numeric values was inefficient in some of the value factories. The efficiency for matching has now been improved using precompiled patterns. (Bug #117027, Bug #37415840)