| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Daniel Farina <daniel(at)heroku(dot)com> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: External Open Standards |
| Date: | 2012-05-21 16:52:45 |
| Message-ID: | 1337619165.5626.5.camel@vanquo.pezone.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On lör, 2012-05-19 at 11:52 -0400, Daniel Farina wrote:
> The documentation is misleading to the point of our support for ISO
> 8601-strict parsing.
>
> http://archives.postgresql.org/pgsql-hackers/2012-02/msg01237.php
>
> A very fine point, but I discovered it not out of curiosity, but a
> fairly angry user on Twitter.
>
> We can define the problem away since the space-inclusive format is so
> common...so much so, that it is codified in RFC 3339
> (http://www.ietf.org/rfc/rfc3339.txt). The only problem, then, is the
> DATESTYLE "ISO" labeling: changing that would be really painful, so
> perhaps another solution is to parse the "T" demanded by 8601,
> presuming no other details come to light.
The problem is that people think that "ISO" means ISO 8601, whereas it
actually means ISO 9075. I can see how that's an easy mistake to make,
though.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-05-21 16:52:59 | Re: Archiver not exiting upon crash |
| Previous Message | Tom Lane | 2012-05-21 16:43:34 | Re: read() returns ERANGE in Mac OS X |