× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



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


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.