Restrictions on the Data Types Involved in Set Operations - Advanced SQL Engine - Teradata Database

SQL Data Manipulation Language

Product
Advanced SQL Engine
Teradata Database
Release Number
17.10
Published
July 2021
Language
English (United States)
Last Update
2021-07-27
dita:mapPath
vjt1596846980081.ditamap
dita:ditavalPath
vjt1596846980081.ditaval
dita:id
B035-1146
lifecycle
previous
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.