From: | "Bima Djaloeis" <bima(dot)djaloeis(dot)uni(at)googlemail(dot)com> |
---|---|
To: | "Douglas McNaught" <doug(at)mcnaught(dot)org> |
Cc: | pgsql-novice(at)postgresql(dot)org, pgsql-general(at)postgresql(dot)org |
Subject: | Re: starting a stored procedure+rule AFTER an insert |
Date: | 2007-10-09 07:51:51 |
Message-ID: | 77f6bcdd0710090051v74bed6b5ncdcbcc8ad8c08e7a@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Thanks for the reply, is there any online reference / tutorial for this?
-BD
2007/10/8, Douglas McNaught <doug(at)mcnaught(dot)org>:
>
> "Bima Djaloeis" <bima(dot)djaloeis(dot)uni(at)googlemail(dot)com> writes:
>
> > I have implemented a stored procedure that writes out the newest DB
> > entry on insert, and combined it with a rule.
> >
> > 1) create function newcache() returns void AS 'newCache', 'newCache'
> language
> > c;
> > 2) create rule newcacherule AS on insert to caches do also select
> newcache();
> >
> > The problem is that newcacherule fires BEFORE the insert has taken
> > place, so effectively, I always just get the 2nd newest entry to
> > write into my text file while the newest entry is "stuck in the
> > queue" until a new insert come. How can I execute my rule AFTER the
> > insert has taken place?
>
> Rules effectively happen at query parse time. You probably want an
> AFTER trigger instead.
>
> -Doug
>
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2007-10-09 08:19:36 | Re: Multiple versions on same box |
Previous Message | A. Kretschmer | 2007-10-09 05:29:55 | Re: Request: Anyone using bogus / "humorous" X-Message-Flag headers, could we please turn them off |