Re: Rules and actions involving multiple rows

Поиск
Список
Период
Сортировка
От Bruce Momjian
Тема Re: Rules and actions involving multiple rows
Дата
Msg-id 200307210421.h6L4LZh26717@candle.pha.pa.us
обсуждение исходный текст
Ответ на Rules and actions involving multiple rows  (Jason Godden <jasongodden@optushome.com.au>)
Список pgsql-general
For me, triggers are for modifying the row being
updated/deleted/inserted, while rules are for modifying other rows as
part of the query.

---------------------------------------------------------------------------

Jason Godden wrote:
> 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
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan if your
>       joining column's datatypes do not match
>

--
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

В списке pgsql-general по дате отправления:

Предыдущее
От: Bruce Momjian
Дата:
Сообщение: Re: Datatypes and performance
Следующее
От: Bruce Momjian
Дата:
Сообщение: Re: Dynamic plpgsql code