Named constraints enable a programmer to debug an embedded SQL or stored procedure application by fetching the name of a violated constraint from the SQLSTATE area. If constraints are not named, determining which constraints belong to which system-defined names can be difficult.
Row-level security constraints must be named. CHECK, UNIQUE, FOREIGN KEY, and PRIMARY KEY constraint specifications must be named.
Constraint names must conform to the rules for Vantage object names and be unique among all other constraint, primary index, and secondary index names specified on the table.
The characters used to
name a constraint can be any of the following:
- Uppercase and lowercase alphabetic characters
- Integers
- Any of the following special characters.
- -
- #
- $
Vantage does not assign system-generated names to unnamed constraints.