| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Alex Pilosov <alex(at)pilosoft(dot)com> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>, Thomas Lockhart <lockhart(at)fourpalms(dot)org> |
| Subject: | Re: timestamp with/without time zone |
| Date: | 2001-06-18 19:00:17 |
| Message-ID: | 200106181900.f5IJ0Hh18159@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> We don't have it. Its just that it is misleading to have 'timestamp with
> time zone' as description of this type, when 'timestamp without time zone'
> does not exist. (Actually, if you try to create a field as 'timestamp
> without time zone', you get timestamp anyway). Since you can't have
> 'without', why mention that the type has a time zone?
>
Totally agree. I see in psql's \dT:
time with time zone | hh:mm:ss, ANSI SQL time
timestamp with time zone | date and time
Looks like 'time' has a similar problem. Let me know if I can help.
--
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 | Alex Pilosov | 2001-06-18 19:03:29 | Re: timestamp with/without time zone |
| Previous Message | Tom Lane | 2001-06-18 18:33:21 | Re: AW: Re: [SQL] behavior of ' = NULL' vs. MySQL vs. Stand ards |