G-9213
🆓Warning
Always follow naming conventions for triggers.
Reason
SQL identifiers share the same namespace as PL/SQL identifiers. 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 for Triggers on Tables and Views
Choose a naming convention that includes:
either
- the name of the object the trigger is added to,
- any of the triggering events:
_br_iudfor Before Row on Insert, Update and Delete_io_idfor Instead of Insert and Delete
or
- the name of the object the trigger is added to,
- the activity done by the trigger,
- the suffix
_trg
Recommendations for System Triggers
Name of the event the trigger is based on.
- Activity done by the trigger
- Suffix
_trg
Examples
ddl_audit_trglogon_trg
Example
Non-Compliant Example
create or replace trigger logon after logon on database begin null; -- some monitoring activity end; /
Issues
| Line | Column | Message |
|---|---|---|
| 1 | 27 | trigger logon does not match '^[a-z][a-z0-9$#_]*_(trg|((b|a)r?|io)_i?u?d?)$'. |
Compliant Solution - ★★★★★
create or replace trigger logon_monitor_trg after logon on database begin null; -- some monitoring activity end; /
Parameters
Use parameters to customize the rule to your needs.
| Parameter | Description | Default Value |
|---|---|---|
| TriggerPattern | Case-insensitive regular expression pattern for SQL triggers. | ^[a-z][a-z0-9$#_]*_(trg|((b|a)r?|io)_i?u?d?)$ |
References
- similar to Trivadis Database Object Naming Conventions - DML / Instead of Trigger
Covers only naming conventions for DML triggers and instead of triggers.
- similar to Trivadis Database Object Naming Conventions - System Trigger
Covers only naming conventions for system triggers.