Question: Mutation in Statement Triggers

Hello,

   I wonder if anyone can help me with the following problem:

   Table 'b' has a statement trigger 't' associated with it that does a query on 'b'. When there is an insert, delete or update on 'b', the trigger executes properly. Table 'b' has a parent table 'a'. The reference from 'b' to 'a' is set to ON DELETE CASCADE. When a row in 'a' is deleted, and Oracle runs off to delete the corresponding rows in 'a', it returns an error saying that 'b' is mutating, and thus it cannot execute the trigger 't'. Any idea why?

Thanks,
Salaam Yitbarek Received on Wed May 31 1995 - 00:00:00 CEST