John, SET TRIGGER XXXXXXXXXXX OFF/ON doesn't fit with the SQL standard.
Also, If you used ABORT TRIGGER in a BEFORE INSERT/UPDATE/DELETE is should cancel execution of the trigger. If that is not happening you should report is as a problem to the RDCC. Jim Bentley American Celiac Society [EMAIL PROTECTED] tel: 1-504-737-3293 --- On Wed, 8/13/08, John Engwer <[EMAIL PROTECTED]> wrote: > From: John Engwer <[EMAIL PROTECTED]> > Subject: [RBASE-L] - Re: Triggers > To: "RBASE-L Mailing List" <[email protected]> > Date: Wednesday, August 13, 2008, 6:09 PM > James and Rachael, > > I have both before and after triggers. I will probably go > with a switch > similar to what Rachael describes. > > It would be nice to have a SET TRIGGER XXXXXXXXXXX OFF/ON > > > > John > > > > From: [email protected] [mailto:[EMAIL PROTECTED] On > Behalf Of Rachael > Malberg > Sent: Wednesday, August 13, 2008 4:37 PM > To: RBASE-L Mailing List > Subject: [RBASE-L] - Re: Triggers > > > > I added this to the start of my triggers.... > > > > set var tv_RunTrig text > > if tv_RunTrig is null then > > set var tv_RunTrig text='Y' > > endif > > > > if tv_RunTrig ='Y' then > > ---run the trigger code > > clear var tv_RunTrig > > endif > > > > then if I'm doing updates that I don't want the > trig to run before updating > I set the var tv_RunTrig='N' > > and clear it after I'm done. > > > > > > ----- Original Message ----- > > From: John Engwer <mailto:[EMAIL PROTECTED]> > > To: RBASE-L Mailing List <mailto:[email protected]> > > Sent: Wednesday, August 13, 2008 2:57 PM > > Subject: [RBASE-L] - Triggers > > > > I use a lot of triggers in my applications and sometimes I > would like to > suppress the trigger for certain processes. Such as the > audit trigger when > updating a large table. Because I usually perform these > procedures at night > when no one else is using the database, I currently drop > the trigger when I > start the routine and then add it back at the end of the > procedure. It > works fine except that the trigger is then not active for > other users that > may log onto the system unexpectedly. > > I think that I may program a switch into the procedure to > bypass the code in > the trigger procedure but I thought that I would ask how > other developers > handle this issue. I tried using the ABORT TRIGGER in the > procedure but it > did not suppress the trigger. > > Any input will be appreciated. > > John
