Re: triggers within commit cycles

["Peter Dow" <pcdow@xxxxxxxxx>]

Hi Joe,

From: "Joe Pluta" <joepluta@PlutaBrothers.com>
> What would be nice is a way to set a flag in a job that says "bypass
> triggers"; if I had that level of granularity in my requests, I'd be very
> happy.

As I mentioned in a previous post, this is easily done. Have the trigger
program test for the existence of a data area (different library list for a
different job would vary whether or not the data area is found), or test for
a job switch, and have it end immediately without doing anything.

Although I'm a bit perturbed by the idea that you would have some jobs where
triggers enforce your business rules, and some jobs where they can bypass
the rules. *Maybe* for data repair, depending on the situation; but in that
case I probably wouldn't want to run the repair while users are on the
system, and I could simply remove the triggers instead of leaving in a back
door.

Regards,
Peter Dow
Dow Software Services, Inc.
909 425-0194 voice
909 425-0196 fax


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com