Implicit UDT-to-DATE Conversion - Teradata Vantage

Teradata® VantageCloud Lake

Deployment
VantageCloud
Edition
Lake
Product
Teradata Vantage
Published
January 2023
Language
English (United States)
Last Update
2024-04-03
dita:mapPath
phg1621910019905.ditamap
dita:ditavalPath
pny1626732985837.ditaval
dita:id
phg1621910019905

Data type conversions involving UDTs require appropriate cast definitions for the UDTs. To define a cast for a UDT, use the CREATE CAST statement.

Performing an implicit data type conversion requires that an appropriate cast definition exists that specifies the AS ASSIGNMENT clause.

Analytics Database performs implicit UDT-to-DATE conversions for the following operations:
  • UPDATE
  • INSERT
  • Passing arguments to stored procedures, external stored procedures, UDFs, and UDMs
  • Specific system operators and functions identified in other sections of this document

If no UDT-to-DATE implicit cast definition exists, Vantage looks for other cast definitions that can substitute for the UDT-to-DATE implicit cast definition:

Combination of Implicit Cast Definitions Description
UDT-to-Numeric UDT-to-Character

(non-CLOB)

 
X   Vantage uses the UDT-to-numeric implicit cast definition.

If multiple UDT-to-numeric implicit cast definitions exist, then Analytics Database returns an SQL error.

  X Vantage uses the UDT-to-character implicit cast definition.

If multiple UDT-to-character implicit cast definitions exist, then Analytics Database returns an SQL error.

X X Analytics Database reports an error.

Substitutions are valid because Analytics Database 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 DATE type.