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 12:52:41 -0400
Message-ID: <15184.1059411161@sss.pgh.pa.us> (raw)
In-Reply-To: <3F2552BF.5060100@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>
Dmitry Tkach <dmitry@openratings.com> writes:
> Why not get rid of 'now' alltogether? Are there any cases when it is
> actually useful as opposed to now()?
Data entry. You don't necessarily have the option to invoke a function,
as opposed to just sending a string for the datetime input parser.
(It would be rather difficult for an application to allow this one case
without permitting SQL-injection attacks, I'd think.)
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: <15184.1059411161@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