From: | Daniel Farina <daniel(at)heroku(dot)com> |
---|---|
To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: External Open Standards |
Date: | 2012-05-19 15:52:50 |
Message-ID: | CAAZKuFbv1ksju0AO6XK2=mRFDXnCkB7TQO7DMovKGdZaG9BoWA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sat, May 12, 2012 at 5:37 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> Do we have a full list of externally defined open standards that we follow?
>
> Are there any known incompatibilities from externally defined open standards?
> (I know about the SQL standard stuff).
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.
--
fdr
From | Date | Subject | |
---|---|---|---|
Next Message | Daniel Farina | 2012-05-19 16:19:36 | Re: Foreign keys in pgbench |
Previous Message | Florian Pflug | 2012-05-19 07:48:51 | Re: read() returns ERANGE in Mac OS X |