From: | "David E(dot) Wheeler" <david(at)justatheory(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Comma Comma Comma 8601 |
Date: | 2013-07-23 16:24:07 |
Message-ID: | ED47660E-16B5-49C7-9514-80487F669B5A@justatheory.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Jul 23, 2013, at 1:17 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Does that create any ambiguities against formats we already support?
> I'm worried about examples like this one:
>
> select 'monday, july 22, 22:30 2013'::timestamptz;
> timestamptz
> ------------------------
> 2013-07-22 22:30:00-04
> (1 row)
>
> Right now I'm pretty sure that the datetime parser treats comma as a
> noise symbol. If that stops being true, we're likely to break some
> applications out there (admittedly, possibly rather strange ones,
> but still ...)
I kind of suspect not, since this fails:
david=# select '12:24:53 654'::time;
ERROR: invalid input syntax for type time: "12:24:53 654"
LINE 1: select '12:24:53 654'::time;
^
I would have guessed that the time parser gets to a state where it knows it is dealing with a ISO-8601-style time. But I have not looked at the code, of course.
David
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2013-07-23 16:27:34 | Re: [COMMITTERS] pgsql: Add support for REFRESH MATERIALIZED VIEW CONCURRENTLY. |
Previous Message | Josh Berkus | 2013-07-23 16:20:40 | Re: [9.4 CF 1] The Commitfest Slacker List |