Re: triggers within commit cycles

["Charly Jones" <charly301@xxxxxxxxxxx>]

>if your trigger executes as part of the transaction,
>then any IO that it does can be covered by the commitment cycle.

Thanks Bruce,

So how do I tell the trigger program to be a part
of the commitment cycle, or not?  Is this on the
Add Physical File Trigger command or is it a
compile option, or what?

Thanks for your help. This is a new area for me.

Charly Jones




>From: "R. Bruce Hoffman, Jr." <rbruceh@attglobal.net>
>
>-----Original Message-----
>From: Charly Jones <charly301@hotmail.com>
>To: midrange-l@midrange.com <midrange-l@midrange.com>
>Date: Monday, August 20, 2001 12:22 PM
>Subject: Re: triggers within commit cycles
>
>
> >
> >But if you use commitment control AND triggers, how
> >do you make sure the right thing happens?
> >
>
>
>Test, my friend, test and test some more...  <vbg>
>
>Commit is something you do... trigger is something
>database does... if your
>trigger executes as part of the transaction, then any IO that it does can
>be
>covered by the commitment cycle. It's no different than calling a program
>or
>procedure to do the "common" stuff around IO. So design, then test and test
>some more.


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