Re: triggers within commit cycles

From: R. Bruce Hoffman, Jr. <rbruceh@attglobal.net>
> From: Leif Svalgaard <leif@leif.org>
> Why complicate an already disasterous situation by trying to correct data
> with another program on the fly with business rules turned off and users
> pounding the database?

the point is that the business rules are only turned off for the repairing
program
not for the production programs. The 'repairing' program could also be a
program
that is testing a new business rule. We may not have a disaster. My point is
that using triggers is too much of an all-or-nothing approach. There are, of
course, many other advantages to use an I/O module instead of raw, native
I/O performed directly by the application programs. I hope we don't need to
have a discussion about that.