From: Jeff Boes <jboes@nexcerpt.com>
To: pgsql-sql@postgresql.org
Subject: Rule won't let me NOTIFY, no matter how hard I try
Date: Tue, 13 Jan 2004 21:07:45 GMT
Message-ID: <2d8491964a9d65324f083494a9f54f8b@news.teranews.com> (raw)
Here's the setup: I wanted to write a rule that would fire on an update
to one table, and do an update to another table, followed by a notify.
My first attempt wasn't acceptable to PG (7.3.4):
create rule "my_rule" as
on update to table_A
where new.col_A != old.col_A
do
(update table_B ...;
notify "my_signal";
);
... because you can't have a "notify" statement in a rule that fires on
update (only select, update, and delete, I guess).
Second attempt was to "hide" the notify in a function:
create function fn_notify(TEXT) returns VOID as '
execute ''notify " || $1 || "'';
' language 'plpgsql';
Oddly enough, this works IF and ONLY IF the rule "my_rule" fires and the
internal update statement does not update any rows. If it actually
updates a row, then I get this error:
WARNING: plpgsql: ERROR during compile of fn_notify near line 5
ERROR: syntax error at or near ""
What gives? Must I use a trigger to get around this?
--
Jeff Boes vox 269.226.9550 ext 24
Database Engineer fax 269.349.9076
Nexcerpt, Inc. http://www.nexcerpt.com
...Nexcerpt... Extend your Expertise
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: jboes@nexcerpt.com
Subject: Re: Rule won't let me NOTIFY, no matter how hard I try
In-Reply-To: <2d8491964a9d65324f083494a9f54f8b@news.teranews.com>
References: <2d8491964a9d65324f083494a9f54f8b@news.teranews.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox