Naming conventions for DB triggers

Question

Are there any naming conventions for DB triggers?

For example "before delete on users" would be "bdUsers" or something like that.

One probable duplicate or related question is: http://stackoverflow.com/questions/7662/ — Tomalak, Jun 01 '09 at 21:07

score 33 · Accepted Answer · answered Jun 01 '09 at 21:06

33

For sorting reasons I would recommend a structured approach:

TR_Users_AD
TR_Users_BD
TR_OtherTable_AI

and so on.

In the end it's up to you - but whatever you choose to do, stay consistent, at least within the same database.

answered Jun 01 '09 at 21:06

Tomalak

10

and keys should be consistent. – JoeCool Apr 03 '12 at 14:03
1

Why don't your example names indicate the type of operation: insert, update, delete? – rory.ap Mar 08 '19 at 16:19
2

@rory They do. "AD" = "After Delete", "BD" = "Before Delete", and so on. – Tomalak Mar 08 '19 at 18:55
2

Why do you insert `TR` for triggers? You do not name table `STUDENT` as `TB_STUDENT`. – Pavel_K May 15 '20 at 09:45

score 24 · Answer 2 · answered Jun 01 '09 at 21:11

24

I agree with @tomalak - but i normally spell out the action at the end instead of abbreviating it...

trig_Users_delete
trig_Users_insert
trig_OtherTable_Insert
trig_OtherTable_InsteadOfInsert

answered Jun 01 '09 at 21:11

Scott Ivey

1

While consistency is key and keys should be consistent, clarity should not be overlooked. – HPWD Jun 11 '19 at 16:01

2 Answers2