G-9205
🆓Warning
Always follow naming conventions for unique constraints.
Reason
All table constraints share the same namespace. Follow naming conventions to prevent naming conflicts, improve readability, and clearly indicate the scope without forcing the use of qualified names. A common practice is to use a prefix and/or suffix to distinguish the identifier types.
Recommendations
Table name or table abbreviation followed by the role of the unique constraint, a _uk and an optional number suffix.
Examples
employees_name_ukdepartments_deptno_uksct_contracts_uksct_coli_uksct_icmd_uk1
Example
Non-Compliant Example
create table emp ( -- ... ename varchar2(14 char) not null, -- ... constraint ename unique (ename) );
Issues
| Line | Column | Message |
|---|---|---|
| 5 | 15 | unique constraint ename does not match '^[a-z][a-z0-9$#_]*_uk\d*$'. |
Compliant Solution - ★★★★★
create table emp ( -- ... ename varchar2(14 char) not null, -- ... constraint emp_ename_uk unique (ename) );
Parameters
Use parameters to customize the rule to your needs.
| Parameter | Description | Default Value |
|---|---|---|
| UniqueConstraintPattern | Case-insensitive regular expression pattern for SQL unique constraints. | ^[a-z][a-z0-9$#_]*_uk\d*$ |