Title: RE: Avoding Mutation of Table trigger
This can be simply solved by eliminating the WHEN condition on the trigger and encapsulating that condition as part of a If .. THEN ... END IF statement.
 
Raj
______________________________________________________

Rajendra Jamadagni              MIS, ESPN Inc.

Rajendra dot Jamadagni at ESPN dot com

Any opinion expressed here is personal and doesn't reflect that of ESPN Inc.

QOTD: Any clod can have facts, but having an opinion is an art!

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Friday, October 11, 2002 12:13 AM
To: Multiple recipients of list ORACLE-L
Subject: Database Trigger not fireing In Delete Mode

Hi all,
 
I have  row level table trigger  to fire on DELETE or INSERT or UPDATE Mode .
It has to fire on certain condition, meaning I have a WHEN condition also.
 
WHEN Condition is like :
       when ( NEW.CR_ACCOUNT is not null and   NEW.CHQ_DT is not null )
 
Since, in DELETE mode NEW value contains null  ,  it does not fire.
 
This Problem would have solved if could write WHEN Condition as
 
       when ((INSERTING or UPDATING) and NEW.CR_ACCOUNT is not null
                  and   NEW.CHQ_DT is not null ) OR
                (DELETING and OLD.CR_ACCOUNT is not null  and   OLD.CHQ_DT is not null )
 
But in WHEN condition one can not write INSERTING or UPDATING.
 
How do i go about it ? Any round about way ?
 
Thanks & Regards.
 
Naba
 
*********************************************************************This e-mail 
message is confidential, intended only for the named recipient(s) above and may 
contain information that is privileged, attorney work product or exempt from 
disclosure under applicable law. If you have received this message in error, or are 
not the named recipient(s), please immediately notify corporate MIS at (860) 766-2000 
and delete this e-mail message from your computer, Thank 
you.*********************************************************************1


Reply via email to