Re: CURRENT_TIMESTAMP wierd behaviour - Mailing list pgsql-general

From Scott Marlowe
Subject Re: CURRENT_TIMESTAMP wierd behaviour
Date
Msg-id 1155224022.20252.142.camel@state.g2switchworks.com
Whole thread Raw
In response to CURRENT_TIMESTAMP wierd behaviour  ("Andy Foster" <andy@fostersontheweb.com>)
List pgsql-general
On Thu, 2006-08-10 at 09:37, Andy Foster wrote:
> Hi all
>
> I have created the following simple table
>
> create table NTE_NOTES (
>     nte_id int unique not null,
>     nte_text text not null,
>     nte_last_updated timestamp not null,
>     constraint nte_pk primary key (nte_id));
>
> If I execute the following sql as a single transaction in the admin
> interface or using JDBC it appears that the CURRENT_TIMESTAMP has the same
> value for all records including the updated one. Why?

Read here:

http://www.postgresql.org/docs/8.1/interactive/functions-datetime.html#FUNCTIONS-DATETIME-CURRENT


pgsql-general by date:

Previous
From: "Andy Foster"
Date:
Subject: CURRENT_TIMESTAMP wierd behaviour
Next
From: Michael Fuhr
Date:
Subject: Re: Tuning to speed select