CREATE CONSTRAINT Syntax Elements - Teradata Vantage

Teradata® VantageCloud Lake
Deployment
VantageCloud
Edition
Lake
Product
Teradata Vantage
Published
January 2023
Language
English (United States)
Last Update
2024-04-03
dita:mapPath
phg1621910019905.ditamap
dita:ditavalPath
pny1626732985837.ditaval
dita:id
phg1621910019905
Unless otherwise noted, every syntax element that is a name must follow the rules for naming database objects. See Object Names.
constraint_name
The name of the row-level security constraint object. The constraint name becomes a column name if you include the constraint in the definition for a table, view, or index.
Constraint names must follow the system rules for database object names, and must be unique among:
  • Constraints defined in the system
  • Column names defined in any table that includes the constraint
data_type
The data type for constraint_name. One of the following:
  • SMALLINT

    Use the SMALLINT data type only for hierarchical (level) constraints.

    The range of valid constraint values is from 1 to 10,000 inclusive.

  • BYTE(n)

    Use the BYTE(n) data type only for non-hierarchical (category) constraints.

    n represents the number of bytes in the constraint value string for a table row. If you do not specify a value for n, the default is 1 byte. The maximum value for n is 32.

    To allow for more categories than the column could otherwise contain, the system automatically expresses each non-hierarchical value as a unique bit position, which allows a table row to contain up to 256 distinct values for the constraint column.

The data type you specify becomes the data type of the associated system-created constraint column in any table to which the constraint is assigned.
NOT
Specifies that a constraint value for a specific table row cannot be null.
NULL
A constraint value for a specific table row can be null.
The default is NULL.
VALUES
The string to follow is a set of name:value pairs, which defines either a hierarchical (level) or non-hierarchical (category) classification system.
The set of name:value pairs defines the set of classifications for the constraint.
The maximum number of name:value pairs depends on whether the constraint is hierarchical (10,000) or non-hierarchical (256).
name
The name of a member of the classification system being defined for the constraint.
One or more of the classification names for the constraint can be assigned to a user or profile to define their access privileges on tables that contain the constraint.
value
The value code for the corresponding name in a name:value pair.
Value codes appear for each row in the corresponding constraint column of tables protected by the constraint.
DELETE, INSERT, SELECT, UPDATE
The SQL operations that can be enforced by a constraint.
You must specify between 1 and 4 SQL operations per constraint definition. Each specified SQL operation must be followed by the SYSLIB.function_name that enforces the operation.
You cannot specify an SQL operation type more than once in a constraint.
SYSLIB.function_name
The name of the UDF that enforces the corresponding DELETE, INSERT, SELECT, or UPDATE operation for the constraint.
The specified UDF must be contained within the SYSLIB database when specified in the constraint definition.
Each UDF named in SYSLIB.function_name specifications for a constraint defines the minimum classification required to perform the associated SQL operation on each row of a table that includes the constraint.