Session Constraint Values in OVERRIDE Sessions - Advanced SQL Engine - Teradata Database

SQL Data Definition Language Syntax and Examples

Product
Advanced SQL Engine
Teradata Database
Release Number
17.00
Published
September 2020
Language
English (United States)
Last Update
2021-01-23
dita:mapPath
wgr1555383704548.ditamap
dita:ditavalPath
lze1555437562152.ditaval
dita:id
B035-1144
lifecycle
previous
Product Category
Teradata Vantage™

The user conducting a session that accesses an RLS table may need OVERRIDE privileges if:

  • The CONSTRAINT object associated with a constraint column in the table does not define a UDF for the SQL operation.
  • Accessing table rows or setting row level constraint values cannot be done effectively with the assigned user defaults.
For additional information on OVERRIDE privileges, see “Working with Constraint OVERRIDE Privileges” in Teradata Vantage™ - Advanced SQL Engine Security Administration, B035-1100.

When an OVERRIDE is in effect for a session:

  • The OVERRIDE privileges bypasses enforcement of the affected UDFs.
  • If the operation is an INSERT or UPDATE, the user SQL must supply the value(s) to be entered into the named constraint column in the table, either using data from the source table or values specified in a SET SESSION CONSTRAINT statement.
Loading tables with non-hierarchical constraints in an OVERRIDE session requires special handling. See Example: Loading Tables with User OVERRIDE Privileges.