Naming Conventions: Avoiding Name Clashes Among UDFs, UDMs, and UDTs - Analytics Database - Teradata Vantage

SQL Data Definition Language Detailed Topics

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
2023-07-11
dita:mapPath
vuk1628111288877.ditamap
dita:ditavalPath
qkf1628213546010.ditaval
dita:id
B035-1184
lifecycle
latest
Product Category
Teradata Vantage™
For UDF, method, and UDT names not to clash, they must observe the following two rules:
  • The following column pair must be unique within the DBC.TVM table:
    • DatabaseID, TVMNameI
  • The signature of the following routine must be unique:
    • database_name.routine_name(parameter_list).

UDFs, methods, and UDTs can have the same SQL names as long as their SPECIFIC names and associated routine signatures are different. In the case of UDTs, the SPECIFIC name reference is to the SPECIFIC names of any method signatures within a UDT definition, not to the UDT itself, which does not have a SPECIFIC name.