Re: This script will crash the connection

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Jan Wieck <janwieck(at)Yahoo(dot)com>, Steve Howe <howe(at)carcass(dot)dhs(dot)org>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: This script will crash the connection
Date: 2001-01-27 05:31:19
Message-ID: 20451.980573479@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> OK, added to TODO:
> * Allow NOTIFY in rules
>>
>> Uh, what does that have to do with the problem? It's certainly not
>> an accurate rendering of either the current or proposed status ...

> Oops, can you give me a line. What was the issue?

"Allow NOTIFY in conditional rules" would be an approximation. It's
not the whole story though, because presently we also have to fail
if the rule is applied to a query with conditions, even if the rule
itself is unconditional. As of my last commit:

regression=# create rule r1 as on update to int4_tbl do notify foo;
CREATE
regression=# update int4_tbl set f1 = f1;
UPDATE 5
regression=# update int4_tbl set f1 = f1 where f1 < 0;
ERROR: Conditional NOTIFY is not implemented

which is pretty ugly but at least it doesn't pretend to do something
it can't, which was the 7.0 behavior. (In 7.0 you'd have gotten a
NOTIFY whether the update updated any rows or not.)

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2001-01-27 05:40:23 Re: This script will crash the connection
Previous Message Tom Lane 2001-01-27 05:25:24 Re: Bug in FOREIGN KEY