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

From: Roberto Mello <rmello(at)cc(dot)usu(dot)edu>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Denis Zaitsev <zzz(at)anda(dot)ru>, pgsql-sql(at)postgresql(dot)org
Subject: Re: Very strange 'now' behaviour in nested triggers.
Date: 2003-07-28 00:27:54
Message-ID: 20030728002754.GD10589@cc.usu.edu
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?

I think that is a preferred behavior.

-Roberto

--
+----| Roberto Mello - http://www.brasileiro.net/ |------+
+ Computer Science Graduate Student, Utah State University +
+ USU Free Software & GNU/Linux Club - http://fslc.usu.edu/ +
øøøøøøøøøøøøøøøøøøøøøøøø-----°*'. (Explosive Tagline)

In response to

Browse pgsql-jdbc by date

  From Date Subject
Next Message Peter Eisentraut 2003-07-28 07:49:41 Passing server_encoding to the client is not future-proof
Previous Message Tom Lane 2003-07-27 15:49:10 Re: Very strange 'now' behaviour in nested triggers.

Browse pgsql-sql by date

  From Date Subject
Next Message Stephan Szabo 2003-07-28 03:47:52 Re: Can a table have a reference to itself?
Previous Message Tom Lane 2003-07-27 15:49:10 Re: Very strange 'now' behaviour in nested triggers.