Date: Wed, 30 Jul 2003 04:05:14 +0600
From: Denis Zaitsev <zzz@anda.ru>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-sql@postgresql.org
Subject: Re: Very strange 'now' behaviour in nested triggers.
Message-ID: <20030730040514.C4870@natasha.ward.six>
References: <20030726193947.B1636@natasha.ward.six>
	<9412.1059229904@sss.pgh.pa.us>
	<20030727020104.A19865@natasha.ward.six>
	<4629.1059320950@sss.pgh.pa.us>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4629.1059320950@sss.pgh.pa.us>;
	from tgl@sss.pgh.pa.us on Sun, Jul 27, 2003 at 11:49:10AM -0400

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...