Re: Comma Comma Comma 8601 - Mailing list pgsql-hackers

From David E. Wheeler
Subject Re: Comma Comma Comma 8601
Date
Msg-id ED47660E-16B5-49C7-9514-80487F669B5A@justatheory.com
Whole thread Raw
In response to Re: Comma Comma Comma 8601  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Comma Comma Comma 8601
List pgsql-hackers
On Jul 23, 2013, at 1:17 AM, Tom Lane <tgl@sss.pgh.pa.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
Ihave not looked at the code, of course. 

David




pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: [9.4 CF 1] The Commitfest Slacker List
Next
From: Kevin Grittner
Date:
Subject: Re: [COMMITTERS] pgsql: Add support for REFRESH MATERIALIZED VIEW CONCURRENTLY.