Generally, I use one trigger program for all events. But I also avoid
doing any major work in a trigger unless ABSOLUTELY necessary. I usually
off-load the needed data to a file or dataq and let a batch process do the
heavy lifting. I have seen systems written that do too much inside
trigger programs and seriously hinder their application's performance.
Brian May
Project Lead
Management Information Systems
Garan, Incorporated
Starkville, Mississippi
Young i Professionals
http://www.youngiprofessionals.com
Charles Wilt <charles.wilt@xxxxxxxxx>
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
02/17/2009 01:47 PM
Please respond to
RPG programming on the IBM i / System i <rpg400-l@xxxxxxxxxxxx>
To
"RPG programming on the AS400 / iSeries" <rpg400-l@xxxxxxxxxxxx>
cc
Subject
Trigger Program Poll
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
midrange.com
