| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | lockhart(at)fourpalms(dot)org |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: timestamp with/without time zone |
| Date: | 2001-07-10 21:38:51 |
| Message-ID: | 200107102138.f6ALcpx10856@candle.pha.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > I believe everyone already agreed that 'current' should be removed.
> > 'invalid' seems somewhat redundant with NULL, so I wouldn't object to
> > taking it out; on the other hand, is it hurting anything? Also, it
> > seems a bad idea to remove it from timestamp if we leave it in abstime;
> > you shouldn't have to worry that casting abstime up to timestamp might
> > fail.
>
> I wouldn't worry about that, since we can now return NULL in the
> translation of abstime to timestamp. otoh we could choose to do the same
> for abstime itself, so 'invalid' is not fundamentally necessary for that
> type anymore either.
Is this a TODO item?
--
Bruce Momjian | http://candle.pha.pa.us
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 | 2001-07-10 21:42:37 | Re: Time to read pg_hba.conf (Re: [PATCHES] [PATCH] Patch to make...) |
| Previous Message | Larry Rosenman | 2001-07-10 21:38:38 | Re: way to pass NEW into function |