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 15184.1059411161@sss.pgh.pa.us
Whole thread Raw
In response to Very strange 'now' behaviour in nested triggers.  (Denis Zaitsev <zzz@anda.ru>)
Responses Re: Very strange 'now' behaviour in nested triggers.  (Dmitry Tkach <dmitry@openratings.com>)
List pgsql-sql
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


pgsql-sql by date:

Previous
From: Bruno Wolff III
Date:
Subject: Re: Problem using Subselect results
Next
From: Josh Berkus
Date:
Subject: Re: Problem using Subselect results