- Passing arguments to stored procedures, external stored procedures, UDFs, and UDMs
- Specific system operators and functions identified in other sections of this document, unless the DisableUDTImplCastForSysFuncOp field of the DBS Control Record is set to TRUE
Performing an implicit data type conversion requires that an appropriate cast definition (see Usage Notes) exists that specifies the AS ASSIGNMENT clause.
The target numeric type of the cast definition does not have to be an exact match to the target numeric type of the implicit conversion. Vantage can use an implicit cast definition that specifies a BYTEINT, SMALLINT, INTEGER, BIGINT, DECIMAL/NUMERIC, NUMBER, or REAL/FLOAT/DOUBLE target type.
If no UDT-to-numeric implicit cast definitions exist, Vantage looks for other cast definitions that can substitute for the UDT-to-numeric implicit cast definition:
|IF the following combination of implicit cast definitions exists …||THEN SQL Engine …|
|X||uses the UDT-to-DATE implicit cast definition.|
|X||uses the UDT-to-character implicit cast definition.
The character type cannot be CLOB.
If multiple UDT-to-character implicit cast definitions exist, then SQL Engine returns an SQL error.
|X||X||reports an error.|
Substitutions are valid because SQL Engine can use the implicit cast definition to cast the UDT to the substitute data type, and then implicitly cast the substitute data type to a numeric type.