Re: Trigger Program Poll

Charles,

That's my experience too.

It makes sense - since all the information required (Event, Time etc.) is
passed as parameters, why bother having 3 different programs? Plus,
typically there will be some similarity to the code for all events
(auditing, etc.).

Rory

On Tue, Feb 17, 2009 at 11:35 AM, Charles Wilt <charles.wilt@xxxxxxxxx>wrote:

All,

Just curious as to others experience,

Of RPG trigger programs I've written and/or looked at most (all?) were
designed to support multiple trigger events and/or times.

In other words, if I've got a file which needs to have a trigger fired
*AFTER *UPDATE, *AFTER *INSERT, and *AFTER *DELETE. I've always just
used/seen single trigger program that handled all three events.
(disregard use of a "Generic Trigger" or "Trigger Mediator")

Has that been your experience or do you see 3 separate programs each
for a specific event?


Interestingly, with SQL triggers you have no option, an SQL trigger
can handle only one event.


Charles
--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.