Restrictions on the Data Types Involved in Set Operations - Analytics Database - Teradata Vantage

SQL Data Manipulation Language

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
VMware
Product
Analytics Database
Teradata Vantage
Release Number
17.20
Published
June 2022
Language
English (United States)
Last Update
2024-04-05
dita:mapPath
pon1628111750298.ditamap
dita:ditavalPath
qkf1628213546010.ditaval
dita:id
esx1472246586715
lifecycle
latest
Product Category
Teradata Vantage™

The following restrictions apply to CLOB, BLOB, and UDT types involved in set operations.

Data Type Restrictions
BLOB

You cannot use set operators with CLOB or BLOB types, except in the case of the UNION ALL set operator.

CLOB
UDT
  • Multiple UDTs involved in set operations must be identical types because Vantage does not perform implicit type conversion on UDTs involved in set operations.

    A workaround for this restriction is to use CREATE CAST to define casts that cast between the UDTs and then explicitly invoke the CAST function within the set operation.

  • UDTs involved in set operations must have ordering definitions.

    Vantage generates ordering functionality for distinct UDTs where the source types are not LOBs. To create an ordering definition for structured UDTs or distinct UDTs where the source types are LOBs, or to replace system-generated ordering functionality, use CREATE ORDERING.

For more information on CREATE CAST and CREATE ORDERING, see Teradata Vantage™ - SQL Data Definition Language Syntax and Examples, B035-1144.