| From: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> |
|---|---|
| To: | Andy Foster <andy(at)fostersontheweb(dot)com> |
| Cc: | pgsql general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: CURRENT_TIMESTAMP wierd behaviour |
| Date: | 2006-08-10 15:33:42 |
| Message-ID: | 1155224022.20252.142.camel@state.g2switchworks.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Fuhr | 2006-08-10 15:34:52 | Re: Tuning to speed select |
| Previous Message | Junkone | 2006-08-10 15:06:00 | How to do auto numbering on INT column |