Like I said I can't modify one of the triggers because it came with a COTS
package and upgrades of the package will overwrite it. I know the docs say
the trigger firing is not necessarily in a particular order, BUT unless
you're going to tell me that they're intentionally randomizing it there has
to be a way to figure it out.
"Roman Mirzaitov" <rmirzaitov_at_kt.kg> wrote in message
news:b2cova$1a7c07$1_at_ID-127142.news.dfncis.de...
> Hi,
>
> from docs:
> "Note: You can create multiple triggers of the same type (BEFORE, AFTER,
or
> INSTEAD OF) that fire for the same
> statement on the same table. The order in which Oracle fires these
triggers
> is __indeterminate__. If your application
> requires that one trigger be fired before another of the same type for the
> same statement, combine these triggers
> into a single trigger whose trigger action performs the trigger actions of
> the original triggers in the appropriate
> order."
>
> Regards,
> --
> Roman Mirzaitov
> Brainbench MVP for Oracle Administration
> www.brainbench.com
>
>
> "Michael" <missed-spam_at_worldnet.att.net> wrote in message
> news:e7j2a.11534$CY6.8200_at_fe06.atl2.webusenet.com...
> > I have two before update row level triggers on a table.
> > Trigger A I can do anything I want to
> > Trigger B came with a COTS package and I can't modify it.
> >
> > How can I make Trigger A always fire first? What determines the firing
> > sequence? Is it something like compilation time?
> >
> >
> >
>
>
Received on Wed Feb 12 2003 - 01:55:08 CST
