Re: Old values in statement triggers?

Поиск
Список
Период
Сортировка
От Josh Kupershmidt
Тема Re: Old values in statement triggers?
Дата
Msg-id AANLkTinxKgSx91a_xcrYCcVxfG-nvu03TrPxOq1H2dLY@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Old values in statement triggers?  (Grzegorz Jaśkiewicz <gryzman@gmail.com>)
Ответы Re: Old values in statement triggers?  (Brian Hirt <bhirt@me.com>)
Список pgsql-general
2010/10/21 Grzegorz Jaśkiewicz <gryzman@gmail.com>:
> OLD.column_name
> NEW.column_name ?

I believe OP is asking specifically about statement-level triggers. As
the docs <http://www.postgresql.org/docs/current/static/trigger-definition.html>
say:

| Statement-level triggers do not currently have any way to
| examine the individual row(s) modified by the statement.

What I've done is to have a row-level trigger that populates a
temporary table with "interesting" changes that need further
processing, and then a statement-level trigger which does bulk-updates
based on what's in that temporary table. This comes in quite handy
when bulk-loading data, e.g. with COPY.

Josh

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

Предыдущее
От: Bruce Momjian
Дата:
Сообщение: Re: 9.0 SSL renegotiation failure restoring data
Следующее
От: Adrian Klaver
Дата:
Сообщение: Re: a query on stored procedures/functions in pgsql