Conditional NOTIFY is not implemented

From: tomas(at)fabula(dot)de
To: pgsql-bugs(at)postgresql(dot)org
Cc: matthew(dot)copeland(at)honeywell(dot)com
Subject: Conditional NOTIFY is not implemented
Date: 2001-09-06 13:15:26
Message-ID: 20010906151526.B23923@www
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

Hi,

Upgrading from 7.0.2 to 7.1.3 (great job, btw!), brought us
some problems. Watch the following:

| versuch=# create table chkntfy (
| versuch(# NUMMER integer default 0 not null,
| versuch(# TEXT varchar(255) default '?' not null
| versuch(# );
| CREATE
| versuch=#
| versuch=# CREATE RULE ru_u_chkntfy AS ON UPDATE TO chkntfy DO NOTIFY CHKNTFY;
| CREATE
| versuch=# insert into chkntfy (nummer,text) values ('1','eins');
| INSERT 110522 1
| versuch=# update chkntfy set nummer=10 where nummer = 1;
| ERROR: Conditional NOTIFY is not implemented
| versuch=#

Matthew Copeland noted the same in pgsql-admin and was told to use triggers
instead of rules. Well, it's a little nuisance, since we don't have statement
triggers (you'd get a notify for each row modified, which in our case can
be a killer.)

Somehow the notify seems to take up the `where' qualifier of the query
triggering the rule (you don't get the error message if you use an unqualified
query).

Is this considered a bug? Is a fix in sight?

Regards
-- tomas

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message pgsql-bugs 2001-09-06 14:29:00 Bug #439: no inherits constraints
Previous Message Michał Pasternak 2001-09-06 10:27:48 Re: ILIKE + OR fault - propably a memory leak

Browse pgsql-hackers by date

  From Date Subject
Next Message David Wheeler 2001-09-06 13:22:22 Re: Bug in createlang?
Previous Message Doug McNaught 2001-09-06 12:39:27 Re: Is there a problem running vacuum in the middle of a transaction?