From: Miguel Carvalho <miguel@ipatimup.pt>
To: pgsql-general@postgresql.org
Cc: pgsql-sql@postgresql.org
Subject: Re: Trigger issue, bug? on 7.2.1
Date: Thu, 20 Mar 2003 12:55:05 -0000 (WET)
Message-ID: <14930.213.13.176.13.1048164905.squirrel@www.ipatimup.pt> (raw)
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>
> "Miguel Carvalho" <miguel@ipatimup.pt> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: miguel@ipatimup.pt, pgsql-general@postgresql.org
Subject: Re: Trigger issue, bug? on 7.2.1
In-Reply-To: <14930.213.13.176.13.1048164905.squirrel@www.ipatimup.pt>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox