From: | Pablo Romero Abiti <pabiti(at)yahoo(dot)com> |
---|---|
To: | Alban Hertroys <dalroi(at)solfertje(dot)student(dot)utwente(dot)nl> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re : Re : Update columns in same table from update trigger? |
Date: | 2011-07-24 13:55:36 |
Message-ID: | 1311515736.14003.YahooMailNeo@web161605.mail.bf1.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Thank you for our help anyway!
________________________________
De : Alban Hertroys <dalroi(at)solfertje(dot)student(dot)utwente(dot)nl>
À : Alban Hertroys <dalroi(at)solfertje(dot)student(dot)utwente(dot)nl>
Cc : Pablo Romero Abiti <pabiti(at)yahoo(dot)com>; "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Envoyé le : Dimanche 24 Juillet 2011 4h06
Objet : Re: Re : [GENERAL] Update columns in same table from update trigger?
On 24 Jul 2011, at 11:00, Alban Hertroys wrote:
> You can't fire a trigger on non-existant data.
I just realised the above statement is a little inexact: you can't fire row-level triggers on non-existant data.
You can still fire statement-level triggers on them, but with those you won't have information about which row(s) were involved, so it won't help your case.
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll see there is no forest.
!DSPAM:1288,4e2be0a412091498931284!
From | Date | Subject | |
---|---|---|---|
Next Message | Chris Travers | 2011-07-24 15:43:48 | Re: Implementing "thick"/"fat" databases |
Previous Message | Sanjay Rao | 2011-07-24 13:25:09 | pgpool HA not working |