RE: Triggers

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
--
[ Picked text/plain from multipart/alternative ]
Mark,

On an insert, it would not matter because the before image does not exist,
however in terms of an update trigger, you could conceivably wish to keep an
audit trail of both before and after images of the data... Not the best
example if you are journaling but for this it will suffice. Conversely on a
delete trigger, the after image would be empty as well!

Well, we can only hope! :-)

-----Original Message-----
From: MWalter@hanoverwire.com [mailto:MWalter@hanoverwire.com]
Sent: Thursday, May 23, 2002 1:47 PM
To: midrange-l@midrange.com
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


Mark Walter
Sr. Programmer/Analyst
Hanover Wire Cloth a div of CCX, Inc.
mwalter@hanoverwire.com
http://www.hanoverwire.com
717.637.3795 Ext.3040

_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.