Re: Very strange 'now' behaviour in nested triggers.

From: Denis Zaitsev <zzz(at)anda(dot)ru>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-sql(at)postgresql(dot)org
Subject: Re: Very strange 'now' behaviour in nested triggers.
Date: 2003-07-29 22:05:14
Message-ID: 20030730040514.C4870@natasha.ward.six
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc pgsql-sql

On Sun, Jul 27, 2003 at 11:49:10AM -0400, Tom Lane wrote:
> I put up a proposal in pgsql-hackers to change this behavior:
> http://archives.postgresql.org/pgsql-hackers/2003-07/msg00818.php
> If we made that change then the "wrong" way of defining the default
> would fail in an obvious fashion --- the 'now' would get reduced to a
> particular time immediately at CREATE TABLE. Doubtless this would annoy
> some people, but the "right" way of defining the default isn't really
> any harder, and it would save folks from getting burnt in corner cases,
> like you were.
>
> Any comments?

The proposed behavious promises to be "strict, simple and
well-defined". The current one definitely tends to have "dirty and
non-obvious side effects here and there". I think the new behaviour
should conquer. BTW, the documentation describes this proposed
behaviour (but why?), not the current one...

In response to

Browse pgsql-jdbc by date

  From Date Subject
Next Message Bruce Momjian 2003-07-30 02:20:16 Re: Very strange 'now' behaviour in nested triggers.
Previous Message Nic 2003-07-29 21:53:22 JDBC stored procs doc patch

Browse pgsql-sql by date

  From Date Subject
Next Message Tom Lane 2003-07-29 22:32:44 Re: Nonexistent NEW relation in some places of rules
Previous Message Denis Zaitsev 2003-07-29 21:33:28 Nonexistent NEW relation in some places of rules