OceanBase Connector/J V2.4.5|V2.4.15|OceanBase Connector/J |docs|OceanBase Documentations

Version information

OceanBase Connector/J V2.4.5 supports PreparedStatement objects that return AutoGeneratedKey and allows the server to detect the client version.

The server can detect the proxy and client versions.
PreparedStatement objects that return AutoGeneratedKey are supported.

Note

To use a PreparedStatement object to return AutoGeneratedKey, make sure that the version of OceanBase Connector/J is V2.4.5 or later and add useOraclePrepareExecute=true to the connection string.
The following table describes the URL parameter changes.

Parameter	Status	Default value	Description	Remarks
compatibleOjdbcVersion	New	6	The compatible Oracle JDBC driver version, which can be set to `6` or `8`. If you set the value of this parameter to another integer, the system does not return an error but still applies the default value.
useInformationSchema	New	false	Specifies whether the driver uses `INFORMATION_SCHEMA` to derive information used by `DatabaseMetaData`.
compatibleMysqlVersion	New	5	The compatible MySQL Connector/J version, which can be set to `5` or `8`. If you set the value of this parameter to another integer, the system does not return an error but still applies the default value.
useOraclePrepareExecute	Optimized	false	Specifies whether to enable both the PreparedStatement and PrepareExecute protocols. In Oracle mode, a `PreparedStatement` object does not communicate with the server before being executed by using `COM_STMT_PREPARE_EXECUTE`.	In the current version, when `useOraclePrepareExecute` is set to `true`, `useServerPrepStmts` is automatically set to `true`. Prior to OceanBase Connector/J V2.4.5, you can enable both the PreparedStatement and PrepareExecute protocols only by manually setting both `useOraclePrepareExecute` and `useServerPrepStmts` to `true`.

Fixed the issue caused by Oracle compatibility processing of the getSchema() method.
Fixed the issue where an error is returned when the JDBC driver tries to establish a connection with the proxy after the SSL protocol and OceanBase Protocol 2.0 are enabled.
Fixed the issue where the error "out of range for column" is returned when useServerPrepStmts is set to false for OceanBase Connector/J.
Fixed the issue where the getInt() or getLong() method does not throw an exception after obtaining overlong data even though jdbcCompliantTruncation=true is configured.
Fixed the issue where the getString() and getTimestamp() methods return null for the zero value of the datetime type. This issue was caused by server modifications.
Fixed the issue where the zero value of the datetime type obtained by the getString() method is different from that in MySQL Connector/J 8.0.