- 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.
- 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.
- SMALLINT
- 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.
- VALUES
- The string to follow is a set of name:value pairs, which defines either a hierarchical (level) or non-hierarchical (category) classification system.
- name
- The name of a member of the classification system being defined for the constraint.
- value
- The value code for the corresponding name in a name:value pair.
- DELETE, INSERT, SELECT, UPDATE
- The SQL operations that can be enforced by a constraint.
- SYSLIB.function_name
- The name of the UDF that enforces the corresponding DELETE, INSERT, SELECT, or UPDATE operation for the constraint.