Re: triggers within commit cycles

["Leif Svalgaard" <leif@xxxxxxxx>]

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).

----- Original Message -----
From: Charly Jones <charly301@hotmail.com>
To: <midrange-l@midrange.com>
Sent: Monday, August 20, 2001 4:21 PM
Subject: Re: triggers within commit cycles


>
> Thanks Bruce,
>
> So... commitment control is really cool and if
> every application was coded using it we would
> have more robust failsafe applications.
>
> And triggers are really cool and allow business logic
> to be an integral part of the database, rather than
> added on with every application and every access
> method.
>
> But if you use commitment control AND triggers, how
> do you make sure the right thing happens?
>
> Charly Jones