| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, hackers(at)postgreSQL(dot)org |
| Subject: | Re: [HACKERS] TODO list |
| Date: | 2000-01-17 16:17:58 |
| Message-ID: | 200001171617.LAA29027@candle.pha.pa.us |
| 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.
Got it. Never mind.
--
Bruce Momjian | http://www.op.net/~candle
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2000-01-17 16:19:59 | Re: [HACKERS] RE: Getting rid of setheapoverride (was Re: [COMMITTERS] heap.c) |
| Previous Message | Bruce Momjian | 2000-01-17 16:17:26 | Re: [HACKERS] Re: [COMMITTERS] pgsql/src/include/catalog (pg_type.h) |