Re: Mutating table and triggers

There is one special case where the the mutating table does not occur, however. I can't remember the exact details at the moment, but it has something to do with the triggering statement guaranteeing (logically) to effect only one row of the table e.g.

    update where primary key = const

--

Jonathan Lewis
Yet another Oracle-related web site: www.jlcomp.demon.co.uk

Terry Dykstra wrote in message <36f1521c.0_at_news.cadvision.com>...
>You cannot override this default behavior. Normally you split the logic
>into a pre and post trigger. In the pre trigger you populate a table a
>pl/sql table with rows that will be affected. The actual update you defer
>to the post trigger, using the pl/sql table to get the actuals rows
>involved.
>
>--
>Terry Dykstra (TeamPS)
>Canadian Forest Oil Ltd.
>Dag Arne Matre wrote in message <01be7155$64892160$4101030a_at_sandeid>...
>>Normally, you cannot do a select on a table within a trigger on the same
>>table (ORA-04091). However, I have this strange feeling having read that
>>this default behavior can be overriden by setting some parameters (or
>>something else). Am I right or wrong?
>>
>>D A
>
>
Received on Thu Mar 18 1999 - 16:10:38 CST