| From: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: timestamptz parsing bug? |
| Date: | 2011-08-29 19:35:25 |
| Message-ID: | 56ACB5A7-DAEB-431B-91E3-10CAC6F8F2BF@kineticode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Aug 29, 2011, at 12:30 PM, Tom Lane wrote:
>> When it gets to the timezone "America/Chicago" at the end, this is
>> handled in the DTK_DATE case, because of the "/". But because ptype is
>> still set, it is expecting this to be an ISO time, so it errors out.
>
> Do we actually *want* to support this? The "T" is supposed to mean that
> the string is strictly ISO-conformant, no?
I didn't realize that appending a time zone was not conformant, but apparently it's not.
http://en.wikipedia.org/wiki/ISO_8601#Time_zone_designators
Only appending a "Z" or an offset seems to be legal. Interesting.
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2011-08-29 19:43:57 | Re: timestamptz parsing bug? |
| Previous Message | Tom Lane | 2011-08-29 19:30:02 | Re: timestamptz parsing bug? |