OceanBase Connector/J V2.4.4

Version information

• Release date: July 10, 2023
• Version: V2.4.4

Overview

OceanBase Connector/J V2.4.4 provides enhanced log diagnostic capabilities and fixes bugs of earlier versions. The version is recommended for general businesses.

Feature enhancements

• The JDBC logging feature is enhanced. I/O logs are distinguished from time consumption logs. JDBC diagnostic capabilities are improved.
• The getIndex(name) method is optimized.
• The internal resource release mechanism is optimized to resolve issues where the number of cursors reaches the upper limit.
• The setFixedCHAR() method is supported. For more information, see com.oceanbase.jdbc.ObPrepareStatement.

Bug fixes

• Fixed the issue where the values obtained by the getScale() and getColumnDisplaySize() methods are inconsistent with those in native Oracle when the precision of NUMBER values is negative.
• Fixed the issue where the return result contains garbled characters when procedures in system tables are queried.
• Fixed the issue where floating-point numbers in composite data types are forcibly converted into integers.
• Fixed the issue of null pointers when the logging feature of OceanBase Connector/J is enabled.
• Fixed the issue where the error "Flag '0'" is returned when you query data of the INTERVAL DAY TO SECOND type in Oracle mode.
• Fixed the issue where the error "java.lang.StringIndexOutOfBoundsException" is returned when the ON DUPLICATE KEY UPDATE statement is used to insert data and the VALUES function is used after ON DUPLICATE KEY UPDATE.
• Fixed the issue where an error is returned when the getString(), getDouble(), getFloat(), or getObject() method is used to obtain invalid values INF, -INF, and NaN of the BINARY_FLOAT or BINARY_DOUBLE data type in Oracle mode.
• Fixed the issue where the error ArrayIndexOutOfBoundsException is returned when a DML statement containing the RETURNING ... INTO ... clause is sent when both the PreparedStatement and PrepareExecute protocols are enabled.
• Fixed the issue where the DatabaseMetaData.getTables() method returns an error when the table name contains backticks (`). MySQL does not return an error in such a case.
• Fixed the issue where values of the DOUBLE type obtained by the getBigDecimal() method are inconsistent with those in native MySQL when the PreparedStatement protocol is enabled.
• Fixed the issue where the getObject(1, OffsetTime.class) method returns an error when serverTimezone=Asia/Shanghai is set.