Release Notes for MariaDB Connector/J 3.0.6

Notable Changes

• The initSql connection parameter has been added. (CONJ-984)

  • The new parameter enables execution of a SQL statement upon connection creation.

  • For example, to execute SET NAMES UTF8 upon connection creation, the following connection string could be used:

  jdbc:mariadb://DB_HOST:DB_PORT/DB?user=DB_USER&password=DB_PASSWD&initSql=SET NAMES UTF8
  

• The pipelining and bulk optimizations can now be used when allowLocalInfile is enabled as long as the statements do not include LOAD LOCAL INFILE commands. Excluding statements that include LOAD LOCAL INFILE commands is done automatically to prevent performance regression. (CONJ-976)

Issues Fixed

• PreparedStatement.getGeneratedKeys() does not return an empty ResultSetobject when no keys are generated by an INSERT. (CONJ-953)

• When a column uses the TIME data typeTIME data type and has a '00:00:00' value, ResultSet.getTime() throws an ArrayIndexOutOfBoundsException if the useServerPrepStmts connection parameter is enabled. (CONJ-975)

• When a column uses the TINYINT(1) data typeTINYINT(1) data type, ResultSet.getObject() returns Byte instead of Boolean. (CONJ-979)

• When a column uses the BIT data typeBIT data type, ResultSet.getObject() returns ByteSet instead of Byte[]. (CONJ-985)

• When a java.util.Date object is passed to PreparedStatement.setObject(), a java.sql.SQLException is thrown with the message "java.util.Date not supported type". (CONJ-980)

Installation

• Install MariaDB Connector/J

Upgrade

MariaDB Connector/J 3.0 has been superseded by MariaDB Connector/J 3.3, which is fully compatible with MariaDB Connector/J 3.0. For upgrade instructions:

• Upgrade from MariaDB Connector/J 2.7 to 3.4

Resources

• Usage Documentation

• Issue Reporting

• Source Code