We have a situation in ORACLE in which we are trying, through the
use of triggers, to do an UPDATE to a parent table cascading to its
children. Our children tables reference a parent table's unique
field, though not the primary key. No matter how we write the
trigger, procedure, etc., we keep getting the MUTATING table error,
even though we do nothing to that table that the trigger was fired
upon, only the children.
Is there any way to keep our Referential Integrity (DELETE CASCADE)
through the table definition, and be able to force some kind of UPDATE
CASCADE, without having to control all our referential integrity
through triggers?
