RE: Trigger question

Which was what I meant, since not all (or even most) programs around here
check to see that the record was changed before doing an UPDATE. Since our
files have a "last changed" date and time, we are now forced to compare the
record to the previous one and only change the timestamp and issue an update
if the before and after images differ. I don't use the trigger itself to do
that; the only thing the trigger does is add records to an audit file.

Francis Lapeyre
IS Dept. Programmer/Analyst
Stewart Enterprises, Inc.
E-mail: flapeyre@xxxxxxxx 



-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Dave Kahn
Sent: Tuesday, March 21, 2006 5:15 AM
To: Midrange Systems Technical Discussion
Subject: Re: Trigger question

On 20/03/06, Lapeyre, Francis <FLAPEYRE@xxxxxxxx> wrote:

> One thing to check, when you added the *UPDATE trigger did you use
> TRGUPDCND(*ALWAYS) (the default)?  I always (sic) change this 
> parameter to *CHANGE - that way, just "looking" at the record without 
> updating it
will
> not force the trigger to fire.

Just "looking" can't cause the update trigger to fire, but updating the
record without changing the contents can. This can be useful on occasion, as
you can force the trigger to fire by using interactive SQL to update a field
to be equal to itself.

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