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.
Enhanced features
- 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 avoid errors when the number of cursors reaches the upper limit.
- The
setFixedCHARmethod is supported. For more information, see com.oceanbase.jdbc.ObPrepareStatement.
Bug fixes
- Fixed a bug that the precision of
NUMBERdata is negative and thegetScaleandgetColumnDisplaySizemethods are inconsistent with those in Oracle databases. - Fixed a bug that the return result contains garbled characters when procedures in system tables are queried.
- Fixed a bug that floating-point numbers in composite data types are forcibly converted into integers.
- Fixed a bug that the protocol contains null pointers.
- Fixed a bug that in Oracle mode, the "Flag '0'" error is returned when you query data of the
INTERVAL DAY TO SECONDtype. - Fixed a bug that the "java.lang.StringIndexOutOfBoundsException" error is returned when you call the
VALUESfunction after you use theON DUPLICATE KEY UPDATEstatement to insert data. - Fixed a bug that in Oracle mode, an error is returned when you use
getString,getDouble,getFloat, orgetObjectto get an invalid value such asINF,-INF, orNaNof theBINARY_FLOATorBINARY_DOUBLEtype. - Fixed a bug that when both the PreparedStatement and PrepareExecute protocols are enabled, the
RETURNING ... INTO ...DML statement returns the "ArrayIndexOutOfBoundsException" error. - Fixed a bug that when a table name is enclosed in backticks (`), the
DatabaseMetaData.getTablesmethod returns an error. This is incompatible with native MySQL Database. - Fixed a bug that when the PreparedStatement protocol is enabled, the
DOUBLEvalue returned by thegetBigDecimalmethod is inconsistent with that in native MySQL Database. - Fixed a bug that when the
serverTimezoneparameter is set toAsia/Shanghai, thegetObject(1, OffsetTime.class)method returns an error.