Data Type Definition
Keyword1
|
|||
---|---|---|---|
DOUBLE4
|
|||
1The CT_PRESERVE= connection argument, which controls how data types are mapped, can affect whether a data type can be defined. The values FORCE (default) and FORCE_COL_SIZE do not affect whether a data type can be defined. The values STRICT and SAFE can result in an error if the requested data type is not native to the data source, or the specified precision or scale is not within the data source range. | |||
2The Oracle data type cannot be defined, and when data is retrieved, the native data type is mapped to a similar data type. | |||
3The timestamp returned by the DATE and TIME data types can be changed to date and time values by using the DATEPART function with the PUT function. | |||
4The ORNUMERIC= connection argument and table option determine how numbers read from or inserted into the Oracle NUMBER column are treated. ORNUMERIC=YES, which is the default, indicates that non-integer values with explicit precision are treated as NUMERIC values. | |||
5The TIMESTAMP(p) data type is not available on Z/OS. | |||
6The VARCHAR2(n) type is supported for up to 32,767 bytes if the Oracle version is 12c and the Oracle MAX_STRING_SIZE= parameter is set to EXTENDED. |