From oracle-l-bounce@freelists.org Fri Sep 23 17:48:46 2005 Return-Path: Received: from air891.startdedicated.com (root@localhost) by orafaq.com (8.12.10/8.12.10) with ESMTP id j8NMmkJG027132 for ; Fri, 23 Sep 2005 17:48:46 -0500 X-ClientAddr: 206.53.239.180 Received: from turing.freelists.org (freelists-180.iquest.net [206.53.239.180]) by air891.startdedicated.com (8.12.10/8.12.10) with ESMTP id j8NMme6H027120 for ; Fri, 23 Sep 2005 17:48:41 -0500 Received: from localhost (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id 2AF631EF01A; Fri, 23 Sep 2005 17:47:53 -0500 (EST) Received: from turing.freelists.org ([127.0.0.1]) by localhost (turing [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 07123-03; Fri, 23 Sep 2005 17:47:53 -0500 (EST) Received: from turing (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id 994271EF123; Fri, 23 Sep 2005 17:47:52 -0500 (EST) From: "David Wendelken" To: Subject: RE: ** chained rows fixing Date: Fri, 23 Sep 2005 18:50:51 -0400 Message-ID: <001801c5c091$3f6fa740$6401a8c0@davidwendelken> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0019_01C5C06F.B85E0740" X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506 In-Reply-To: AAAAAORZ18h9lqdCtv4yP58C4dAkHEwA X-archive-position: 25850 X-ecartis-version: Ecartis v1.0.0 Sender: oracle-l-bounce@freelists.org Errors-To: oracle-l-bounce@freelists.org X-original-sender: davewendelken@earthlink.net Precedence: normal Reply-To: davewendelken@earthlink.net X-list: oracle-l X-Virus-Scanned: by amavisd-new-20030616-p9 (Debian) at avenirtech.net X-mailscan-MailScanner-Information: Please contact the ISP for more information X-mailscan-MailScanner: Found to be clean X-MailScanner-From: oracle-l-bounce@freelists.org X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on air891.startdedicated.com X-Spam-Status: No, hits=-2.9 required=5.0 tests=AWL,BAYES_00,HTML_50_60, HTML_FONTCOLOR_BLUE,HTML_FONTCOLOR_UNKNOWN,HTML_MESSAGE autolearn=no version=2.63 ------=_NextPart_000_0019_01C5C06F.B85E0740 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable 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 =20 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.=20 To disable triggers would require that rest of application be shut = down.=20 =20 =20 ------=_NextPart_000_0019_01C5C06F.B85E0740 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message
More=20 accurately, you should set up a mechanism to be able to turn off = individual=20 business logic components invoked by the trigger, NOT just the=20 trigger.
Otherwise, you may find yourself in need of keeping some logic = in place=20 but not others... :)
-----Original Message-----

While this = doesn't=20 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. =20 It's made our lives *so* much easier.

-----Original=20 Message-----
Subject: **=20 chained rows fixing

 

Hi,

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

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

 

 

<= /HTML> ------=_NextPart_000_0019_01C5C06F.B85E0740-- -- http://www.freelists.org/webpage/oracle-l