how instead of triger is helpful for mutating tables errors handlling ?

how instead of triger is helpful for mutating tables errors
handlling ?

Question Posted / sudhir

2 Answers
10503 Views
Oracle, I also Faced
E-Mail Answers

Answers were Sorted based on User's Feedback

how instead of triger is helpful for mutating tables errors handlling ?..

Answer / guru

"Mutating" means "changing". A mutating table is a table
that is currently being modified by an update, delete, or
insert
statement. When a trigger tries to reference a table that is
in state of flux (being changed), it is considered
"mutating" and
raises an error since Oracle should not return data that has
not yet reached its final state.
Another way this error can occur is if the trigger has
statements to change the primary, foreign or unique key
columns of the
table off which it fires. If you must have triggers on
tables that have referential constraints, the workaround is
to enforce the
referential integrity through triggers as well.
There are several restrictions in Oracle regarding triggers:
• A row-level trigger cannot query or modify a
mutating table. (Of course, NEW and OLD still can be
accessed by the
trigger) .
• A statement-level trigger cannot query or modify a
mutating table if the trigger is fired as the result of a
CASCADE delete.

So some time we can not use triggers to put DMl operations
on table. that time we can use INSTEAD OF TRIGGER.

Is This Answer Correct ?

7 Yes

0 No

how instead of triger is helpful for mutating tables errors handlling ?..

Answer / mahesh

create a view (simple view) on mutating table

write a tigger on view (define similar to table)

Know try to do dml operations on table

it will not show the mutating error

Is This Answer Correct ?

2 Yes

2 No

Post New Answer