Re: [HACKERS] rule/notify bug?
| От | Tom Lane |
|---|---|
| Тема | Re: [HACKERS] rule/notify bug? |
| Дата | |
| Msg-id | 28730.894061403@sss.pgh.pa.us обсуждение исходный текст |
| Ответ на | rule/notify bug? (Brett McCormickS <brett@abraxas.scene.com>) |
| Список | pgsql-hackers |
Brett McCormickS <brett@abraxas.scene.com> writes:
> create rule radius1 as on update to user where (current.usrppp <> new.usrppp) do notify radius;
> update user set usrname = 'Brett McCormick' where usrid = 'brett';
> NOTIFY
> the notification comes through on the radius relation
> (which, interestingly, doesn't exist)
Yup, that's what you told it to do: "notify radius". Listen/notify
names are really arbitrary identifiers, not relation names. This
is a good thing: you can signal conditions that aren't tightly
tied to a single table.
> should I be filling out a bug report? ;)
It's not a bug, it's a feature ;-)
The listen/notify documentation could be clearer about this, though.
Maybe it's a documentation bug.
regards, tom lane
В списке pgsql-hackers по дате отправления: