Tom Lane wrote:
> The above is a pretty bad idea in any case --- think about what happens
> when you have some data in the table. It'll set *every row* to id = 1
> and data = 'test'.
Your right, DUH, I forgot my where clause in my example. It is in the
real query though, perhaps I didn't get e
Matthew Schumacher <[EMAIL PROTECTED]> writes:
> update test set id = 1, data = 'test';
The above is a pretty bad idea in any case --- think about what happens
when you have some data in the table. It'll set *every row* to id = 1
and data = 'test'. The reason nothing happens when there is nothin
Tom Lane wrote:
> Matthew Schumacher <[EMAIL PROTECTED]> writes:
>
>>I'm having trouble getting the rule system to work on updates that do
>>not match the where clause.
>
>
> You did not say what you mean by "doesn't work", but what I suspect you
> are getting bit by is that ON UPDATE rules fire
Matthew Schumacher <[EMAIL PROTECTED]> writes:
> I'm having trouble getting the rule system to work on updates that do
> not match the where clause.
You did not say what you mean by "doesn't work", but what I suspect you
are getting bit by is that ON UPDATE rules fire before the original
query is
I'm having trouble getting the rule system to work on updates that do
not match the where clause. Perhaps I'm doing this wrong, but I can't
find any docs that explain this very clearly.
Here what I would like to do:
CREATE OR REPLACE RULE
insertAcctUpdate
AS ON UPDATE TO
accounting_tab
WHERE
