On fre, 2012-02-24 at 10:40 -0800, Daniel Farina wrote:
> On Fri, Feb 24, 2012 at 4:45 AM, Peter Eisentraut wrote:
> > On tor, 2012-02-23 at 23:41 -0800, Daniel Farina wrote:
> >> As it turns out, evidence would suggests that the "ISO" output in
> >> Postgres isn't, unless there's an ISO standard
On Fri, Feb 24, 2012 at 4:45 AM, Peter Eisentraut wrote:
> On tor, 2012-02-23 at 23:41 -0800, Daniel Farina wrote:
>> As it turns out, evidence would suggests that the "ISO" output in
>> Postgres isn't, unless there's an ISO standard for date and time that
>> is referring to other than 8601.
>
> Y
On tor, 2012-02-23 at 23:41 -0800, Daniel Farina wrote:
> As it turns out, evidence would suggests that the "ISO" output in
> Postgres isn't, unless there's an ISO standard for date and time that
> is referring to other than 8601.
Yes, ISO 9075, the SQL standard. This particular issue has been
di
As it turns out, evidence would suggests that the "ISO" output in
Postgres isn't, unless there's an ISO standard for date and time that
is referring to other than 8601. It does not permit use of a space
between the date and the time, as seen in:
SELECT now();
now
---
