G-9207
🆓Warning
Always follow naming conventions for check 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 column and/or role of the check constraint, a _ck and an optional number suffix.
Examples
employees_salary_min_ckorders_mode_ck
Example
Non-Compliant Example
create table emp ( -- ... sal number(7,2), constraint emp_sal check (sal > 0) );
Issues
| Line | Column | Message |
|---|---|---|
| 4 | 15 | check constraint emp_sal does not match '(?i)^[a-z][a-z0-9$#_]*_ck$'. |
Compliant Solution - ★★★★★
create table emp ( -- ... sal number(7,2), constraint emp_sal_gt_zero_ck check (sal > 0) );
Parameters
Use parameters to customize the rule to your needs.
| Parameter | Description | Default Value |
|---|---|---|
| CheckConstraintPattern | Regular expression pattern for SQL check constraints. | (?i)^[a-z][a-z0-9$#_]*_ck$ |