Re: values from now() in the same transaction

From: Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)net>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: values from now() in the same transaction
Date: 2007-02-17 00:42:29
Message-ID: 45D64F75.3060106@cox.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 02/16/07 17:25, Chris Browne wrote:
> zelvlad(at)yahoo(dot)com (Vladimir Zelinski) writes:
>> I tried function now(),current_timestamp() but all of
>> them behave similar.
>>
>> I don't believe that it's bug, probably it's a feature
>> of the postgreSql database.
>
> Indeed, that is intentional. CURRENT_TIMESTAMP and NOW() return the

Ooooh, is that Standard Behavior?

Is there a standard definition for CURRENT_TIMESTAMP?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFF1k91S9HxQb37XmcRAqFsAKCMI+xzFxig2XMDPcsWcRMfToOJ/QCffWwO
iLBhZIc3jGp2VWwVSxW7hRQ=
=RTIl
-----END PGP SIGNATURE-----

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Bruce Momjian 2007-02-17 01:23:48 Re: user input during runtime
Previous Message Alvaro Herrera 2007-02-17 00:30:28 Re: Anticipatory privileges