Re: [HACKERS] Why DEFAULT text 'now' does not work for TIMESTAMP columns - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [HACKERS] Why DEFAULT text 'now' does not work for TIMESTAMP columns
Date
Msg-id 27359.932399706@sss.pgh.pa.us
Whole thread Raw
In response to Re: [HACKERS] Why DEFAULT text 'now' does not work for TIMESTAMP columns  (Thomas Lockhart <lockhart@alumni.caltech.edu>)
List pgsql-hackers
Thomas Lockhart <lockhart@alumni.caltech.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


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] CVS
Next
From: "Ansley, Michael"
Date:
Subject: RE: [HACKERS] CVS