Re: triggers

From: Frank <franjoe_at_frisurf.no>
Date: Sat, 21 Jul 2001 21:29:02 GMT
Message-ID: <T%%07.2982$tD1.390859@news3.oke.nextra.no>

Hi!

It could be useful to know a little bit about the reason for this "problem". One thing that come to my mind, is that you put your logic from the different triggers into a package,
with one procedure for each of the logics from the triggers. You can probably use some package-global
variables to "flag" your way around. Call one "scheduler" procedure from each of your triggers
(possibly you have to add to trigger name/event to its parameters so you know where you are called from)
The scheduler can set flags indicating which triggers have been run and not. A after row/statement trigger must
reset all flags after. One problem with my proposal here, is that if you can do all this to your application,
then it just as well have been better to put all logic in one trigger with the logic in correct sequence (?)

Frank

Orban Anita <anita.orban_at_sysdata.siemens.hu> wrote in message news:3B448100.79D64414_at_sysdata.siemens.hu...
> Hello Everybody,
>
> Does anybody know how to reach: a trigger to be fired before an other
> one.
> They are declared on the same event, so they both should be fired
> "before delete" on the same table.
>
> Thanks for any idea you have...
> regards, Anita
>
Received on Sat Jul 21 2001 - 16:29:02 CDT