G-9206
🆓Warning
Always follow naming conventions for foreign key 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/abbreviation followed by referenced table name/abbreviation followed by a _fk and an optional number suffix.
Examples
empl_dept_fksct_icmd_ic_fk1
Example
Non-Compliant Example
create table parent ( parent_id raw(16) default sys_guid() not null, -- ... constraint parent_pk primary key (parent_id) ); create table child ( -- ... parent_id raw(16) not null, constraint child_parent foreign key (parent_id) references parent );
Issues
| Line | Column | Message |
|---|---|---|
| 10 | 15 | foreign key child_parent does not match '^[a-z][a-z0-9$#_]*_fk\d*$'. |
Compliant Solution - ★★★★★
create table parent ( parent_id raw(16) default sys_guid() not null, -- ... constraint parent_pk primary key (parent_id) ); create table child ( -- ... parent_id raw(16) not null, constraint child_parent_fk foreign key (parent_id) references parent );
Parameters
Use parameters to customize the rule to your needs.
| Parameter | Description | Default Value |
|---|---|---|
| ForeignKeyConstraintPattern | Case-insensitive regular expression pattern for SQL foreign key constraints. | ^[a-z][a-z0-9$#_]*_fk\d*$ |