Re: External Open Standards - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: External Open Standards
Date
Msg-id 1337619165.5626.5.camel@vanquo.pezone.net
Whole thread Raw
In response to Re: External Open Standards  (Daniel Farina <daniel@heroku.com>)
Responses Re: External Open Standards
List 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.



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: read() returns ERANGE in Mac OS X
Next
From: Tom Lane
Date:
Subject: Re: Archiver not exiting upon crash