Version information
Release date: December 15, 2022
Version: V2.4.1
Overview
OceanBase Connector/J V2.4.1 integrates the rich client feature in V2.3.0 and fixes many issues related to compatibility with MySQL. This version applies to general businesses.
Feature enhancements
- The rich client feature is integrated into the driver to provide the routing logic of OceanBase Database Proxy (ODP). This way, business requests are calculated in the driver and directly routed to the target OBServer node. As no load balancer is required, the access links are short.
- The following URL parameters are provided:
obProxySocket,clobberStreamingResults,maxRows,zeroDateTimeBehavior,allowNanAndInf,defaultConnectionAttributesBanList, andenableOb20Checksum. - A Java virtual machine (JVM) parameter is provided for you to export the headers of OceanBase Protocol 2.0 on the console.
- A parameter is provided for you to enable and disable checksum verification based on OceanBase Protocol 2.0.
Bug fixes
- Fixed some MySQL compatibility issues.
- Fixed the issue where the
setDate()method triggers an exception when binary write is enabled. - Fixed the issue where if you set a value of the STRING type in an ARRAY or STRUCT object to another object type, the value is forcibly converted and an error is returned.
- Fixed the issue where the
getSchema()method throws a NullPointerException (NPE) upon connection if you do not specifyschemain the URL in Oracle mode. - Fixed the issue where an error occurs when you call the
getObject()method to obtain data.
Notice
OceanBase Connector/J of this version uses some methods of the DatabaseMetaData interface, such as getProcedures(), getTables(), getSchemas(), getColumns(), getFunctions(), getTablePrivileges(), getPrimaryKeys(), getBestRowldentifier(), getColumnPrivileges(), and getXXXKeys(), to return a result set. A call to close() will cause infinite recursion.