From: | "Miguel Carvalho" <miguel(at)ipatimup(dot)pt> |
---|---|
To: | <pgsql-general(at)postgresql(dot)org> |
Cc: | <pgsql-sql(at)postgresql(dot)org> |
Subject: | Re: Trigger issue, bug? on 7.2.1 |
Date: | 2003-03-20 12:55:05 |
Message-ID: | 14930.213.13.176.13.1048164905.squirrel@www.ipatimup.pt |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-sql |
> "Miguel Carvalho" <miguel(at)ipatimup(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Sullivan | 2003-03-20 13:29:05 | Re: log_timestamp and SIGHUP? |
Previous Message | Daniel R. Anderson | 2003-03-20 12:44:39 | Re: PostgreSQL downloads compressed with bzip2 instead of |
From | Date | Subject | |
---|---|---|---|
Next Message | Mike Meyer | 2003-03-20 13:52:44 | Rule for updating through a view. |
Previous Message | paul_smith1 | 2003-03-20 12:46:37 | SQL stored proc query (optimising) |