16.20 - Session Constraint Values in OVERRIDE Sessions - Teradata Database - Teradata Vantage NewSQL Engine

Teradata Vantage™ SQL Data Definition Language Syntax and Examples

Product
Teradata Database
Teradata Vantage NewSQL Engine
Release Number
16.20
Published
March 2019
Content Type
Programming Reference
Publication ID
B035-1144-162K
Language
English (United States)
Last Update
2019-05-24

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™ NewSQL 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.