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.
Date: Wed, 30 Jul 2003 04:05:14 +0600
Message-ID: <20030730040514.C4870@natasha.ward.six> (raw)
In-Reply-To: <4629.1059320950@sss.pgh.pa.us>
References: <20030726193947.B1636@natasha.ward.six>
<9412.1059229904@sss.pgh.pa.us>
<20030727020104.A19865@natasha.ward.six>
<4629.1059320950@sss.pgh.pa.us>
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...
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: zzz@anda.ru, tgl@sss.pgh.pa.us
Subject: Re: Very strange 'now' behaviour in nested triggers.
In-Reply-To: <20030730040514.C4870@natasha.ward.six>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox