| From: | Peter Childs <blue(dot)dragon(at)blueyonder(dot)co(dot)uk> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Peter Childs <blue(dot)dragon(at)blueyonder(dot)co(dot)uk>, Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>, "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Trigger |
| Date: | 2003-10-23 15:30:00 |
| Message-ID: | Pine.LNX.4.58.0310231628170.15748@bluedragon.homelinux.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, 23 Oct 2003, Tom Lane wrote:
> Peter Childs <blue(dot)dragon(at)blueyonder(dot)co(dot)uk> writes:
> > Great idea shame drivers to get at these are rare. Anyway you
> > still need a trigger to fire the notify and these get sent when the query
> > is done not when its commented. hmmm
>
> But the NOTIFY isn't delivered until and unless the transaction commits.
> This gets around the AFTER-trigger-can-still-roll-back problem.
>
> regards, tom lane
>
Notify is also not very flexable it tells you somthing has
triggerged it not the information that a trigger is supplied with, like
what has changed to what from what.
Peter Childs
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Richard Huxton | 2003-10-23 15:32:05 | Re: Setting up DSPACE for Postgres access |
| Previous Message | scott.marlowe | 2003-10-23 15:22:30 | Re: Recomended FS |