Re: triggers within commit cycles

["Charly Jones" <charly301@xxxxxxxxxxx>]

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



>From: "R. Bruce Hoffman, Jr." <rbruceh@attglobal.net>
>-----Original Message-----
>From: Charly Jones <charly301@hotmail.com>
>
> >If I update a record in a file that has an update
> > trigger, then rollback the
> >transaction using commitment control, does the >trigger program fire
>again
> >with the correct update that puts the record >back like it was?
> >
> >And does a delete that is rolled back fire the >trigger program again, if
> >there is a delete trigger?
> >
> >And does an add that is rolled back cause the >trigger program to fire
>with a
> >delete of the just added record?
> >
>
>uh... no, no, no
>



_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp