15.10 - Using ALTER FUNCTION or REPLACE FUNCTION with Row-Level Security UDFs - Teradata Database

Teradata Database SQL Data Definition Language Syntax and Examples

prodname
Teradata Database
vrm_release
15.10
created_date
December 2015
category
Programming Reference
featnum
B035-1144-151K

If you use ALTER FUNCTION or REPLACE FUNCTION on a row-level security UDF, the resulting UDF must retain all parameters specified in the constraint definitions that use the UDF.

Example: Setting the Protection Mode of a UDF to EXECUTE NOT PROTECTED

You have created and successfully debugged a UDF named TransXML and you now want to set its protection mode to EXECUTE NOT PROTECTED. The following request assumes there is no other UDF in the database named TransXML:
     ALTER FUNCTION TransXML EXECUTE NOT PROTECTED;

Example: Setting a Recompiled UDF to EXECUTE NOT PROTECTED

An existing UDF named XPathValue must be recompiled for some reason. XPathValue had previously been set to run in unprotected mode. Recompiling a UDF always resets its protection mode back to protected, so you must follow any recompilation with another ALTER FUNCTION request to set its protection mode back to unprotected.

These statements recompile XPathValue and then set its protection mode back to unprotected:
     ALTER FUNCTION XPathValue COMPILE;
     ALTER FUNCTION XPathValue EXECUTE NOT PROTECTED;