Default Timestamp 'Now' bug with 7.4 on Panther.

From: Harry Hochheiser <hsh(at)nih(dot)gov>
To: pgsql-bugs(at)postgresql(dot)org
Cc: Harry Hochheiser <hsh(at)nih(dot)gov>, siah(at)nih(dot)gov
Subject: Default Timestamp 'Now' bug with 7.4 on Panther.
Date: 2004-02-12 20:21:34
Message-ID: 0D406079-5D99-11D8-BDC7-0003938AD324@nih.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


Running Postgres 7.4 on Panther, there seems to be a problem with
setting a timestamp column to have a default of 'now':

createdb test

create table bar (date timestamp DEFAULT 'now');
insert into bar DEFAULT VALUES;
insert into bar DEFAULT VALUES;
insert into bar DEFAULT VALUES;
insert into bar DEFAULT VALUES;

select * from BAR;

output:

date
----------------------------
2004-02-12 15:17:38.838411
2004-02-12 15:17:38.838411
2004-02-12 15:17:38.838411
2004-02-12 15:17:38.838411

All rows have the same timestamp, as if 'now' was interpreted at the
time of table creation, not at the time of insertion.

thanks,

Harry

Harry Hochheiser, Ph.D.
Image Informatics and Computational Biology Unit
Laboratory of Genetics
NIH, National Institute on Aging
333 Cassell Drive
Suite 3000
Baltimore MD 21224
410 558 8046

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Garrett Dangerfield 2004-02-12 22:04:05 copy problem
Previous Message Javier Carlos 2004-02-12 18:46:27 Problem with datatype REAL using the = (EQUAL) operator