Re: -- TABLE is mutating -- AAAGHHHHHHHHH!
From: Jim Kennedy <kennedy-down_with_spammers_at_attbi.com>
Date: Tue, 17 Jun 2003 13:38:30 GMT
Message-ID: <qREHa.10196$vq.2322_at_sccrnsc04>
Date: Tue, 17 Jun 2003 13:38:30 GMT
Message-ID: <qREHa.10196$vq.2322_at_sccrnsc04>
Yes. Write a package and have a member of that package that is a variable that holds if the table is mutating.
So when you enter before trigger set the variable to 0 ( not mutating)
When you enter the after row trigger then set the variable to 1 (mutating).
In the trigger for table B look at the state of the package varaible and act
accordingly.
Jim
-- Replace part of the email address: kennedy-down_with_spammers_at_attbi.com with family. Remove the negative part, keep the minus sign. You can figure it out. "Andre" <avanrossem_at_hotmail.com> wrote in message news:4d32d1be.0306170315.24f0cf84_at_posting.google.com...Received on Tue Jun 17 2003 - 15:38:30 CEST
> Hello all,
>
> I have a triggers which is executed on an update of tabel A.
> In the trigger I update TableB. The update trigger AGAIN updates table
> A.
>
> Well, As Expected the "ORA-04091: table A is mutating,
> trigger/function may not see it"-error occurs. No problem.
>
> But, I want to include some code in triggerB that sais:
> "If tableA is mutating then do nothing"
>
> Is this possible??
>
>
> Thanks,
> Andre van Rossem