Duplicate Triggers
Sree, February 02, 2011 - 9:24 am UTC
Wow! that seems like an horrible solution from Oracle[??] If your trigger fired before my trigger, and MV logs were updated or refreshed before my trigger fired, that MV doesn't have uptodate data then. Seems so wrong..but may be I'm missing a point.
Anyways, Oralce 11G got the order clause atleast :-)
Thanks foryour response.
February 02, 2011 - 10:16 am UTC
It would not work that way - the triggers are an AFTER FOR EACH ROW trigger
By the time you get to the after triggers - the data for that row is stabilized, you can only modify the data in the BEFORE FOR EACH ROW trigger.
It worked as designed.
Duplicate triggers
Sree, February 02, 2011 - 4:03 pm UTC
Yes, you are correct. After update would have all the changes by then..missed it.
But, thanks for the explanation
Duplicate triggers
Ravi, February 03, 2011 - 5:08 am UTC
Hi ,
Order of trigger fire is the same order as it created, i had check the same example given in this question .
It is working in the order of trigger creation in oracle 10g.
February 03, 2011 - 3:30 pm UTC
unless you can show me documentation that states it is a support fact that they fire in creation order - you better NOT rely on it.
Until 11g you must assume the firing order is random and not deterministic.
All it takes is one application bug fix, one administrative operation, anything - and the order you relied on will change. Do not rely on side effects.