RE: ** chained rows fixing

More accurately, you should set up a mechanism to be able to turn off individual business logic components invoked by the trigger, NOT just the trigger.
Otherwise, you may find yourself in need of keeping some logic in place but not others... :)

-----Original Message-----

While this doesn't help you now I highly recommend a company standard of having a package variable that's checked at the beginning of each trigger as you mention. It's made our lives *so* much easier.

-----Original Message-----

Subject: ** chained rows fixing  

Hi,

   I need to get rid of chained rows for some tables. Re-insert (delete and insert) the rows. Some of the tables have triggers so it is difficult. IS there a way to execute the delete and insert without the triggers firing. Meaning is there a way to make sure trigger does not fire for a session. One way would be to declare a package variable and check it in the beginning of a trigger but that would need change to all triggers.

  To disable triggers would require that rest of application be shut down.     

--
http://www.freelists.org/webpage/oracle-l