rule/notify bug?
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)
linux 2.0.33, postgresql 6.3.2..
should I be filling out a bug report? ;)
or just using gdb
creating the table & dropping and recreating the rule has no effect
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
Import Notes
Reply to msg id not found: YourmessageofFri1May1998134532-0700199805012045.NAA13404@abraxas.scene.com | Resolved by subject fallback