Re: [HACKERS] Why DEFAULT text 'now' does not work for TIMESTAMP columns

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] Why DEFAULT text 'now' does not work for TIMESTAMP columns
Date: 1999-07-19 15:55:06
Message-ID: 27359.932399706@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> writes:
>> As long as both sets of names are accepted, I think it probably wouldn't
>> matter if the implementation of one of them changes. I wouldn't like to
>> have my tables containing "datetime" suddenly stop working though...

> No, we would have the names aliased in the parser, as we do for
> int->int4, etc.

Oh, I see. And so my next pg_dump output would magically have the
standard names. That's cool.

>>>> And while you are being annoyed by code, how about looking at problems
>>>> with trying to use indices on constants and on functions calls?
>> "Indices on constants"? I'm confused...

> I just phrased it poorly. I was referring to the int2_col = int4_val
> problem...

Ah. I've got that on my to-do list, but I've got no good idea for a
solution yet... see prior traffic...

regards, tom lane

Browse pgsql-hackers by date

  From Date Subject
Next Message Ansley, Michael 1999-07-19 16:27:21 RE: [HACKERS] CVS
Previous Message Tom Lane 1999-07-19 15:41:23 Re: [HACKERS] CVS