| From: | Sean Reifschneider <jafo(at)tummy(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: Problem with RULE to update tables |
| Date: | 2003-03-18 07:18:41 |
| Message-ID: | 20030318071841.GA23282@tummy.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Mon, Mar 17, 2003 at 02:41:29PM -0500, Tom Lane wrote:
>Yup. A rule is invoked once per query, not once per operated-on record.
>You'll find that a trigger acts more like what you are expecting.
Ah, yeah, that seems to work exactly as expected. At least, my tests
now pass successfully after converting from a rule to a trigger. It was
a pain that trigger functions can't be SQL. I just wanted to run some
SQL after the delete/insert/update, and ended up having to wrap it in
a pl/python function...
Thanks,
Sean
--
"Isn't having a smoking section in a restaurant kind of like having a
peeing section in a swimming pool?" -- David Broadfoot
Sean Reifschneider, Inimitably Superfluous <jafo(at)tummy(dot)com>
tummy.com, ltd. - Linux Consulting since 1995. Qmail, Python, SysAdmin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurent FAILLIE | 2003-03-18 10:13:52 | Re: Solution for bug #899 |
| Previous Message | Bruce Momjian | 2003-03-18 01:49:09 | Re: Bug #890: only one user per process in libpq with krb5 auth |