Re: Recommendation: One or multiple triggers

From: <michael_bialik_at_my-deja.com>
Date: Thu, 02 Sep 1999 19:29:20 GMT
Message-ID: <7qmj5v$ak$1@nnrp1.deja.com>

Hi.
To add something :
For multiple triggers firing on the same event ( ON UPDATE, etc. ) you are going to pay in performance : additional resources needed to invoke these triggers.

Michael.

In article <936175013.15990.0.pluto.d4ee154e_at_news.demon.nl>, "Sybrand Bakker" <postmaster_at_sybrandb.nospam.demon.nl> wrote:
> Hi Nicolas,
>
> One important thing to know: the order in which triggers for the same
event
> fire is NOT guaranteed.
> So if you split up, make sure there are no logical dependencies, ie
one
> trigger is expect to fire first.
> IMO, I would split up only when I was forced to, eg. triggers being
> generated by third party software (I am in that situation now).
> In all other cases, if the trigger code gets too complicated, split
it up in
> procedures.
>
> Hth,
>
> --
> Sybrand Bakker, Oracle DBA
> Nicolas Bronke <news_at_trinity.de> wrote in message
> news:37ccc9b6_at_news.uk.ibm.net...
> > Does exist a recommendation to use only one trigger or multiple?
> >
> > E.g.
> > For a table it can exists more than one trigger e.g. (before update
etc.)
> > Is it better to include all features in one trigger or exist some
reasons
> to
> > split the functionallities into seperate triggers?
> >
> > Regards
> > Nicolas Bronke
> >
> >
>
>

Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't. Received on Thu Sep 02 1999 - 14:29:20 CDT