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

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

> > 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...
                   - Thomas

-- 
Thomas Lockhart                lockhart@alumni.caltech.edu
South Pasadena, California


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] Why DEFAULT text 'now' does not work for TIMESTAMP columns
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] New version number 6.6 or 7.0