Re: triggers within commit cycles

["R. Bruce Hoffman, Jr." <rbruceh@xxxxxxxxxxxxx>]

-----Original Message-----
From: Joe Pluta <joepluta@PlutaBrothers.com>
To: midrange-l@midrange.com <midrange-l@midrange.com>
Date: Tuesday, August 21, 2001 1:14 PM
Subject: RE: triggers within commit cycles


>I suppose.  Don't ask me, I wouldn't use triggers for business rules.  If I
>can write a trigger program, I can write an external I/O module.  The only
>reason to use triggers for business rules is so that you can have things
>like DFU and SQL updates as part of your production systems.

And a program with a write statement instead of calling that I/O module is
the same thing as executing DFU. It will circumvent your business rules. I
know this could start a holy war, that's not my intention.

IMO, neither is perfect, but I have a better chance with my business rules
in triggers than I do with an externalized I/O module. Even if I'm in an
object oriented language.

As for this particular argument about which is better, I will not respond to
any further bait.

===========================================================
R. Bruce Hoffman, Jr.
 -- IBM Certified Specialist - AS/400 Administrator
 -- IBM Certified Specialist - RPG IV Developer

"America is the land that fought for freedom and then
  began passing laws to get rid of it."

     - Alfred E. Neuman