From: Tom Lane <tgl@sss.pgh.pa.us>
To: Dmitry Tkach <dmitry@openratings.com>
Cc: Denis Zaitsev <zzz@anda.ru>
Cc: pgsql-sql@postgresql.org
Subject: Re: Very strange 'now' behaviour in nested triggers.
Date: Mon, 28 Jul 2003 13:12:53 -0400
Message-ID: <15800.1059412373@sss.pgh.pa.us> (raw)
In-Reply-To: <3F255813.1000401@openratings.com>
References: <20030726193947.B1636@natasha.ward.six>
<9412.1059229904@sss.pgh.pa.us>
<20030727020104.A19865@natasha.ward.six>
<4629.1059320950@sss.pgh.pa.us>
<3F2552BF.5060100@openratings.com>
<15184.1059411161@sss.pgh.pa.us>
<3F255813.1000401@openratings.com>
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
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: tgl@sss.pgh.pa.us, dmitry@openratings.com, zzz@anda.ru
Subject: Re: Very strange 'now' behaviour in nested triggers.
In-Reply-To: <15800.1059412373@sss.pgh.pa.us>
* 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