Re: Recommendation: One or multiple triggers

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
>
>
Received on Wed Sep 01 1999 - 03:36:12 CDT