| From: | Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | hackers(at)postgreSQL(dot)org |
| Subject: | Re: [HACKERS] TODO list |
| Date: | 2000-01-17 08:31:52 |
| Message-ID: | 3882D378.71F6A86@alumni.caltech.edu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> I was meaning to ask you which of the date/time types are going to be
> left standing when the dust settles. (I know you've said, but the
> archives are so messed up right now that I can't find it.)
> Timestamp is the only remaining standard type without an array type,
> and if it's not going to be deprecated then it ought to have one...
"timestamp" will continue, but *all* of the code will come from a
renamed "datetime". So don't bother adding anything for timestamp,
since it will magically appear when datetime gets renamed.
btw, I will make "datetime" a synonym for "timestamp", so existing
apps should work without change.
- Thomas
--
Thomas Lockhart lockhart(at)alumni(dot)caltech(dot)edu
South Pasadena, California
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hiroshi Inoue | 2000-01-17 09:25:06 | RE: [HACKERS] RE: Getting rid of setheapoverride (was Re: [COMMITTERS] heap.c) |
| Previous Message | Thomas Lockhart | 2000-01-17 08:26:28 | Re: [COMMITTERS] pgsql/src/include/catalog (pg_type.h) |