The following table summarizes connection properties which can be used to handle data types.

Table 1. Data type handling properties
Property Characteristic

ConvertNull

 Controls how data conversions are handled for null values.

By default, the driver checks the data type this is requested against the data type of the table column that stores the data. If a conversion between the requested type and column type is not defined, the driver generates an "unsupported data conversion" exception regardless of the data type of the column value.

FetchTSWTZasTimestamp

 Determines whether column values with the datetimeoffset data type are returned as a JDBC VARCHAR or TIMESTAMP data type.

If set to true, column values with the datetimeoffset data type are returned as a JDBC TIMESTAMP data type.

If set to false, column values with the datetimeoffset data type are returned as a JDBC VARCHAR data type.

The default is false.

JavaDoubleToString

 Determines which algorithm the driver uses when converting a double or float value to a string value.

If set to true, the driver uses the JVM algorithm when converting a double or float value to a string value. If your application cannot accept rounding differences and you are willing to sacrifice performance, set this value to true to use the JVM conversion algorithm.

If set to false, the driver uses its own internal algorithm when converting a double or float value to a string value. This value improves performance, but slight rounding differences within the allowable error of the double and float data types can occur when compared to the same conversion using the JVM algorithm.

By default, the driver uses its own internal conversion algorithm, which improves performance.

JDBCBehavior

 Determines how the driver describes database data types that map to the following JDBC 4.0 data types: NCHAR, NVARCHAR, NLONGVARCHAR, NCLOB, and SQLXML.

If set to 0, the driver describes the data types as JDBC 4.0 data types.

If set to 1, the driver describes the data types using JDBC 3.0-equivalent data types.

By default, the driver describes the data types using JDBC 3.0-equivalent data types. This allows your application to continue using JDBC 3.0 types. Additionally, the PROCEDURE_NAME column contains procedure name qualifiers. For example, for the fully qualified procedure named 1.sp_productadd, the driver would return sp_productadd;1.

SupportBinaryXML

 Enables the driver to support XMLType with binary storage on servers running Oracle 12c and higher.