| From: | Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| 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:23:44 |
| Message-ID: | 37934300.366D8AFC@alumni.caltech.edu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)alumni(dot)caltech(dot)edu
South Pasadena, California
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 1999-07-19 15:30:25 | Re: [HACKERS] New version number 6.6 or 7.0 |
| Previous Message | Tom Lane | 1999-07-19 15:05:23 | Re: [HACKERS] Why DEFAULT text 'now' does not work for TIMESTAMP columns |