Rules and actions involving multiple rows - Mailing list pgsql-general

From Jason Godden
Subject Rules and actions involving multiple rows
Date
Msg-id 200307061448.59366.jasongodden@optushome.com.au
Whole thread Raw
Responses Re: Rules and actions involving multiple rows  (Alvaro Herrera <alvherre@dcc.uchile.cl>)
Re: Rules and actions involving multiple rows  (Dmitry Tkach <dmitry@openratings.com>)
Re: Rules and actions involving multiple rows  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-general
Hi All,

Just have a quick question regarding rules:

In the past I've always used triggers to fire before or after events however I
see that the same thing can be achieved through rules (for logging etc...) so
I created a rule which fires on update (not DO INSTEAD) however it only seems
to work for a single row - whereas the triggers work for all rows updated in
a transaction.  Is this correct and if so I presume I should be sticking to
triggers if I want this kind of behaviour?

Rgds,

Jason

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Record locking in deadlock
Next
From: Alvaro Herrera
Date:
Subject: Re: Rules and actions involving multiple rows