Re: Using OLD on INSERT

Поиск
Список
Период
Сортировка
От Terry Lee Tucker
Тема Re: Using OLD on INSERT
Дата
Msg-id 200401220839.07572.terry@esc1.com
обсуждение исходный текст
Ответ на Using OLD on INSERT  (Paul Makepeace <postgresql.org@paulm.com>)
Ответы Re: Using OLD on INSERT  (Terry Lee Tucker <terry@esc1.com>)
Список pgsql-novice
We check the value of TG_OP as in:
IF TG_OP = ''UPDATE'' THEN
    Code that address OLD and NEW here;
ELSE
    Code that addresses only NEW here.
END IF;

On Thursday 22 January 2004 08:29 am, Paul Makepeace wrote:
> I have a trigger that sets an expires column to
> last_access+expiry::interval if expires IS NULL or if the expires value
> isn't being set or changed.
>
>   IF NEW.expires IS NULL OR NEW.expires = OLD.expires THEN
>       NEW.expires = NEW.last_access+NEW.expiry:interval;
>   END IF;
>
> The problem here is OLD doesn't exist on the first INSERT which throws
> an error. It seems PL/pgSQL doesn't have C's short-circuit booleans.
>
> a) Is there a way around this?
> b) is there a 'right' way to determine if a column is being changed?
>
> Paul (total PL/pgSQL newbie)

--
Quote: 8
"Even now politicians use the phrase 'federal dollars' as a synonym for
 'free money.' It's a dangerous tendency, for it leaves the states
 accountable to Washington rather than to their own voters. This mix of
 state and federal governments is not just economically suspect but
 politically corrosive; it undermines the essence of real federalism:
 the integrity of both state and federal governments. If we're serious
 about states' rights, then we need to get serious about states'
 responsibilities. The two go together. As with love and marriage, you
 can't have one without the other."

 --Paul Greenberg

 Work: 1-336-372-6812
 Cell: 1-336-363-4719
email: terry@esc1.com

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

Предыдущее
От: Iandé Coutinho
Дата:
Сообщение: executing backup remotly
Следующее
От: Terry Lee Tucker
Дата:
Сообщение: Re: Using OLD on INSERT