Skip site navigation (1) Skip section navigation (2)

Re: Default Timestamp 'Now' bug with 7.4 on Panther.

From: Harry Hochheiser <hsh(at)nih(dot)gov>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org, siah(at)nih(dot)gov
Subject: Re: Default Timestamp 'Now' bug with 7.4 on Panther.
Date: 2004-02-16 15:38:01
Message-ID: 1A91AEA0-6096-11D8-BF7C-0003938AD324@nih.gov (view raw or flat)
Thread:
Lists: pgsql-bugs
Ok, thanks. that's what i get for using a premade package, I guess.

-harry

On Feb 15, 2004, at 1:31 PM, Tom Lane wrote:

> Harry Hochheiser <hsh(at)nih(dot)gov> writes:
>> Running Postgres 7.4 on Panther, there seems to be a problem with
>> setting a timestamp column to have a default of 'now':
>
> There was an intentional change of behavior --- see the release notes.
> The supported way to do this is to use CURRENT_TIMESTAMP or now() as
> the column default.
>
> 			regards, tom lane
>


In response to

pgsql-bugs by date

Next:From: Pavel StehuleDate: 2004-02-17 10:48:35
Subject: plpgsql - variable's names conflict with table field names
Previous:From: Chris CampbellDate: 2004-02-15 21:50:41
Subject: Crash when calling a pl/pgsql function with no row to pass as an argument

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group