UDF Restrictions | CREATE/REPLACE FUNCTION | Teradata Vantage - Usage Restrictions for User-Defined Functions - 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™
UDF usage is restricted as follows:
  • If the UDF library for your database contains any objects with multibyte characters in their name, you cannot use a single-byte session character set to create a new UDF, UDT, method, or Java external procedure object even if the new object name contains only single-byte characters. Instead, use a multibyte session character set.
  • You cannot perform a CREATE FUNCTION or REPLACE FUNCTION request from an embedded SQL application.
  • A UDF cannot reference a recursive view.
  • A row-level security policy can only be a scalar function.
  • You cannot call a row-level security policy function from a DML request.

    Row-level security policy UDFs can only be specified for columns in a CREATE TABLE or ALTER TABLE request.

  • Non-Java UDFs can specify both distinct and structured UDTs as input and return parameters.
  • If you specify a UDT as either an input parameter or as the function result, the current user of the function must have either the UDTUSAGE privilege on the SYSUDTLIB database or the UDTUSAGE privilege on the specified UDT.
  • UDFs that are used as cast routines, ordering routines, or transform routines must be contained within the SYSUDTLIB database.
  • Java UDFs cannot be called from within a Java external procedure.