Re: Very strange 'now' behaviour in nested triggers. - Mailing list pgsql-sql

From Tom Lane
Subject Re: Very strange 'now' behaviour in nested triggers.
Date
Msg-id 15800.1059412373@sss.pgh.pa.us
Whole thread Raw
In response to Very strange 'now' behaviour in nested triggers.  (Denis Zaitsev <zzz@anda.ru>)
List pgsql-sql
Dmitry Tkach <dmitry@openratings.com> writes:
> Does it mean that the *application* (not the database) user would then 
> have to know the exact specific way to represent the current time in his 
> data entry form?
> Such an application looks like (how do I say it politely?) not a very 
> user-friendly one to me :-)

So?  "now()" is certainly not more user-friendly than "now".  My point
is that wherever you are making the decision that you want to input
current time, there may be layers between you and the database that will
only want to pass data-value strings and not function invocations.
        regards, tom lane


pgsql-sql by date:

Previous
From: Dmitry Tkach
Date:
Subject: Re: Very strange 'now' behaviour in nested triggers.
Next
From: Dmitry Tkach
Date:
Subject: Re: Very strange 'now' behaviour in nested triggers.