Re: CURRENT_TIMESTAMP not work correctly insinde a transaction. - Mailing list pgsql-bugs

From Peter Eisentraut
Subject Re: CURRENT_TIMESTAMP not work correctly insinde a transaction.
Date
Msg-id Pine.LNX.4.30.0202221702050.686-100000@peter.localdomain
Whole thread Raw
In response to Re: CURRENT_TIMESTAMP not work correctly insinde a transaction.  (Thomas Lockhart <lockhart@fourpalms.org>)
Responses Re: CURRENT_TIMESTAMP not work correctly insinde a transaction.
List pgsql-bugs
Thomas Lockhart writes:

> > In a transaction until you commit your transaction through a jdbc
> > connection, each time you use the Current_timestamp (or 'now'), the
> > timestamps is always the same, and when your transaction is very long you
> > have undesirable effect.
>
> This is not a bug, but the behavior required by SQL9x afaicr.

AFAIK, this is PostgreSQL bugward compatibility.  SQL says that
current_timestamp returns the "current timestamp", which you can interpret
any way you want to.

--
Peter Eisentraut   peter_e@gmx.net

pgsql-bugs by date:

Previous
From: Thomas Lockhart
Date:
Subject: Re: CURRENT_TIMESTAMP not work correctly insinde a transaction.
Next
From: Coax
Date:
Subject: Possible bug concerning LASTOID in 7.2