CONSTRAINT - Analytics Database - Teradata Vantage

SQL Data Definition Language Syntax and Examples

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
2024-10-04
dita:mapPath
jco1628111346878.ditamap
dita:ditavalPath
qkf1628213546010.ditaval
dita:id
mdr1472255012272
lifecycle
latest
Product Category
Teradata Vantage™

Assign one or more row-level security constraints to the user_name.

There is a limit of 6 hierarchical constraints and 2 non-hierarchical constraints that can be assigned per user.

For more information about row-level security constraints, see CREATE CONSTRAINT.

row_level_security_constraint_column_name
Name of one or more row-level security constraints, each one followed by the list of the hierarchical levels or non-hierarchical categories, valid for the constraint, which are being assigned to the user_name.
  • Example hierarchical constraint assignment:
    CONSTRAINT = Classification_Level (Secret, Unclassified DEFAULT),
  • Example non-hierarchical constraint assignment:
    CONSTRAINT = Classification_Country (US, UK, GER)
level_name
Hierarchical levels, valid for the constraint, which are being assigned to the user_name.
DEFAULT
DEFAULT can be specified for 1 classification level from the specified list of level names for a hierarchical constraint. The specified level becomes the default value for the constraint when a session is established for the user.
If you do not specify DEFAULT for any of the listed classification levels, then the first level listed becomes the default for the user.
DEFAULT is not valid for non-hierarchical category constraints.
category_name
Non-hierarchical categories, valid for the constraint, which are being assigned to the user_name.
NULL