skip to main content
Using the driver : Using connection properties : Data type handling properties
  

Try DataDirect Drivers Now

Data type handling properties

The following table summarizes connection properties which can be used to handle data types.
Table 7. Data type handling properties
Property
Characteristic
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.
Specifies how the driver describes the data type for Date/Time/Timestamp input parameters.
By default, the driver uses the following rules to describe the data type of Date/Time/Timestamp input parameters:
*If an input parameter is set using setDate(), the driver describes it as date.
*If an input parameter is set using setTime(), the driver describes it as time.
*If an input parameter is set using setTimestamp(), the driver describes it as datetimeoffset.
Specifies how the driver describes the data type for Date/Time/Timestamp output parameters.
By default, the driver uses the following rules to describe the data type of Date/Time/Timestamp output parameters:
*If an output parameter is set using setDate(), the driver describes it as date.
*If an output parameter is set using setTime(), the driver describes it as time.
*If an output parameter is set using setTimestamp(), the driver describes it as datetimeoffset.
Determines whether the driver attempts to determine, at execute time, which data type to use to send input parameters to the database server. Sending parameters as the data type the database expects improves performance and prevents locking issues caused by data type mismatches.
By default, the driver does not attempt to describe input parameters and sends String and Date/Time/Timestamp input parameters to the server as specified by the StringInputParameterType and DateTimeInputParameterType properties.
Determines whether the driver attempts to determine, at execute time, which data type to use to send output parameters to the database server. Sending parameters as the data type the database expects improves performance and prevents locking issues caused by data type mismatches.
By default, the driver does not attempt to describe output parameters and sends String and Date/Time/Timestamp output parameters to the server as specified by the StringOutputParameterType and DateTimeOutputParameterType properties.
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.
Determines whether the driver returns column values for the native TIME data type as the JDBC TIME or TIMESTAMP data type.
If set to true, the driver returns column values for the native TIME data type as the JDBC TIME data type. The fractional seconds portion of the value is truncated when the value is returned in the java.sql.Time object.
If set to false, the driver returns column values for the native TIME data type as the JDBC TIMESTAMP data type. The Java Epoch (Jan 1,1970) is returned in the date portion.
The default is false.
Determines which algorithm the driver uses when converting a double or float value to a string value.
By default, the driver uses its own internal conversion algorithm, which improves performance.
Determines how the driver describes database data types that map to the following JDBC 4.0 data types: NCHAR, NVARCHAR, NLONGVARCHAR, NCLOB, and SQLXML.
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 in a Java SE 6 or higher environment. 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.
Determines whether the driver maps XML data to the LONGVARCHAR or LONGVARBINARY data type.