X-Original-To: pgsql-general@postgresql.org Received: from mail.ipatimup.pt (link.ipatimup.up.pt [193.137.37.4]) by postgresql.org (Postfix) with ESMTP id C322D475B99; Thu, 20 Mar 2003 07:45:42 -0500 (EST) Received: from ipatimup.pt (localhost [127.0.0.1]) by mail.ipatimup.pt (8.11.6/IPATIMUP) with SMTP id h2KCt5v19256; Thu, 20 Mar 2003 12:55:05 GMT X-RAV-AntiVirus: This e-mail has been scanned for viruses on host: mail.ipatimup.pt Received: from 213.13.176.13 (proxying for 10.20.110.138) (SquirrelMail authenticated user miguel) by www.ipatimup.pt with HTTP; Thu, 20 Mar 2003 12:55:05 -0000 (WET) Message-ID: <14930.213.13.176.13.1048164905.squirrel@www.ipatimup.pt> Date: Thu, 20 Mar 2003 12:55:05 -0000 (WET) Subject: Re: Trigger issue, bug? on 7.2.1 From: "Miguel Carvalho" To: In-Reply-To: <19094.1047998060@sss.pgh.pa.us> References: <2108.213.13.176.13.1047995196.squirrel@www.ipatimup.pt> <19094.1047998060@sss.pgh.pa.us> X-Priority: 3 Importance: Normal Cc: Reply-To: miguel@ipatimup.pt X-Mailer: SquirrelMail (version 1.2.X) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Archive-Number: 200303/970 X-Sequence-Number: 39462 > "Miguel Carvalho" writes: >> The trigger code will force another trigger fire because of the >> changes in the record. I'm i right? > > No, altering the NEW record doesn't cause any additional trigger > firings. If it did, such a trigger would be infinitely recursive. > I see your point, you are completely right! > Your DELETE issued by the trigger would cause firing of ON DELETE > triggers, but not another firing of ON UPDATE. You are right, too. When i was repplying to your message, after stripping some lines of the trigger code, i have found that the second trigger fire ( not actualy a real trigger fire ) was caused by a bad logic in the trigger code. Thank's to all for the repplies. Regards Miguel Carvalho