Re: triggers within commit cycles

true, but then as Bruce points out, you may not want to
do these things in the production environment :-)
It is, of course, still possible to combine the I/O
module with the trigger approach for the simplest
forms of business rules. All, I'm saying is that
encapsulating the I/O allows you considerable
freedom of separation of business logic and
I/O stuff.
Please, I should have kept my big mouth shut,
I don't really want to have this discussion. One
can drag a horse to water, but it is hard forcing
him to drink...


----- Original Message -----
From: Peter Dow <pcdow@yahoo.com>
To: <midrange-l@midrange.com>
Sent: Monday, August 20, 2001 2:39 PM
Subject: Re: triggers within commit cycles


> But this doesn't protect you from DFU, WRKDBF, DBU, interactive SQL, etc.
> etc. or any program that doesn't use the modules. You can turn off triggers
> by simply removing them, or  you could even have them testing a data area
> for a particular value or simply existence.
>
> From: "Leif Svalgaard" <leif@leif.org>
> > There is a simpler (better?) way of doing this:
> > Have an access module for every file or table
> > you use. Place the business rules in the module
> > (could even be turned on/off by a switch in the
> > calling sequence - sometimes you don't want
> > any rules, e.g. during emergency repair of
> > data in the file).
>
>
>
> _________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
>