From: | "Thomas G(dot) Lockhart" <lockhart(at)alumni(dot)caltech(dot)edu> |
---|---|
To: | "Henry B(dot) Hotz" <hotz(at)jpl(dot)nasa(dot)gov> |
Cc: | Brett McCormickS <brett(at)abraxas(dot)scene(dot)com>, pgsql-hackers(at)hub(dot)org |
Subject: | Re: [HACKERS] datetime default 'now' broken? |
Date: | 1998-03-17 02:35:32 |
Message-ID: | 350DE174.19E1738D@alumni.caltech.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> >> 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.
Hi Henry. You're missing a lot by not upgrading. DEFAULT clauses on
tables which Brett was asking about aren't even available pre-v6.2. The
'now' behavior in default clauses was an unexpected side-effect of the
optimizer, which evaluates things which look like constants before
execution.
Give me a call during the day at x47797 if you have any other
reservations about upgrading...
- Tom
From | Date | Subject | |
---|---|---|---|
Next Message | The Hermit Hacker | 1998-03-17 02:47:57 | Re: [HACKERS] Re: [PATCHES] patches for 6.2.1p6 |
Previous Message | Jackson, DeJuan | 1998-03-17 02:14:09 | RE: [HACKERS] RE: [QUESTIONS] The Complete and Ccomprehensive lis t of Newbie qu |