Re: [HACKERS] datetime default 'now' broken?

From: "Henry B(dot) Hotz" <hotz(at)jpl(dot)nasa(dot)gov>
To: "Thomas G(dot) Lockhart" <lockhart(at)alumni(dot)caltech(dot)edu>, Brett McCormickS <brett(at)abraxas(dot)scene(dot)com>
Cc: pgsql-hackers(at)hub(dot)org
Subject: Re: [HACKERS] datetime default 'now' broken?
Date: 1998-03-16 20:48:07
Message-ID: v03130309b13340398d9e@[137.78.218.94]
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

At 9:59 PM -0800 3/15/98, Thomas G. Lockhart wrote:
>> If I create a table with a datetime field with a default of 'now',
>> every insert the value is the time of table creation instead of the
>> time of insert, which is how it behaved in previous releases (I think
>> this was even documented).
>
>I can't recall it ever working that way, though before we discovered
>that it didn't we all assumed that it _did_ work that way :)
>

I'm running 6.1.1 and I *depend* on 'now' giving me the real now in an
insert. I guess I'm glad I never upgraded.

Signature failed Preliminary Design Review.
Feasibility of a new signature is currently being evaluated.
h(dot)b(dot)hotz(at)jpl(dot)nasa(dot)gov, or hbhotz(at)oxy(dot)edu

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message PostgreSQL On Peanuts.roanoke.edu 1998-03-16 21:09:24 AUTOINDEXING AND HOROLOGY REGRESSION ERROR ON PGSQL 6.3, LINUX-ELF i686
Previous Message Peter T Mount 1998-03-16 18:53:17 Re: [QUESTIONS] Re: [HACKERS] text should be a blob field