Okay ... unless old.table2.col_1 = new.table2.col_2 the trigger won't
fire.
I don't see anything wrong here ....
Raj
--------------------------------------------------------------------------------
Rajendra dot Jamadagni at nospamespn dot com
All Views expressed in this email are strictly personal.
QOTD: Any clod can have facts, having an opinion is an art !
Rajendra dot Jamadagni at nospamespn dot com
All Views expressed in this email are strictly personal.
QOTD: Any clod can have facts, having an opinion is an art !
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Monday, June 09, 2003 2:54 PM
To: Multiple recipients of list ORACLE-L
Subject: Cascading Triggers
Hi listers...
I have a question related to triggers. One of the developers here has created two triggers as follows :
Trigger #1 is an AFTER UPDATE trigger on TABLE-A
- the trigger has PL/SQL code including an UPDATE dml statement on TABLE-B.COL-2
Trigger #2 is an AFTER UPDATE trigger on TABLE-B with a WHEN clause (old.COL-1 = new.COL-2)
- the trigger has PL/SQL including an UPDATE to TABLE-C
So, here's the interesting thing...
An update to TABLE-A fires Trigger #1 causing an update to TABLE-B.COL-2.
This should in turn cause Trigger #2 to fire. But that is not happening, or perhaps its fired, but
the WHEN clause condition on TABLE-B (Trigger #2) isn't being met for some reason.
The question is why ? Is there something going on with read consistancy ? Where Trigger #2 sees
the old (pre-updated) version of TABLE-B.COL-2 and is not aware of the new value set by Trigger #1 ?
I haven't seen much info on cascading triggers.
Any thoughts or suggestions to point me in the right direction would be appreciated.
Carol
<<attachment: ATT03622.gif>>
*********************************************************************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
