RE: Triggers

[Jim Langston <jlangston@xxxxxxxxxxx>]

If you need to modify the record that is to be written, you do a *before
trigger so you can change the data record that is to be written.

If you don't need to modify the record that is to be written, then I use
*after triggers.

Regards,

Jim Langston

-----Original Message-----
Subject: Triggers

Hello all,

What are the advantages, if any, of *before *insert as compared to *after
*Insert trigger programs? Or doesn't it really matter? I am using the
trigger to write an audit record. There is no validation or business logic
going on here. The only thing I can think of is that the database insert
will complete if using a *after trigger if the trigger program were to fail
for some reason.


Thanks,

Mark