Re: How can I avoid a recursive trigger?

Well, if possible I'd rework the design to make my life easier. If not, you may need to create a temporary table from the original and join that, or else select it into a pl/sql table in memory if it's not too big. For performance reasons though, you should minimise the work the triggers have to do.
Sorry it's not an easy answer.

"Ovind Osengen" <oeo_at_rocketmail.com> wrote in message news:970ulg$5im$1_at_oslo-nntp.eunet.no...
> To deal with the ORA-04091 Mutating table error, I decomposed a trigger
 into
> 3 triggers, i.e. before statement, before each row and after statement
> triggers in addition to a package for trigger state. This method is
> described by several authors.
>
> However I need an insert or update or delete trigger, this is less
 described
> in the litterature. E.g. when an insert occurs, a field in the triggering
> table is updated by the trigger, this value depends on other records in
 the
> same table. The update in the after statement trigger fires another update
> trigger that results in recursion ( ORA-00036 ), however this is not
> intended. What is a good approach to avoid this? Any links?
>
> Thanks
> Ovind
>
>
>
>
Received on Wed Feb 21 2001 - 20:32:32 CST