From: | Daniel Farina <daniel(at)heroku(dot)com> |
---|---|
To: | Brendan Jurd <direvus(at)gmail(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 05:42:31 |
Message-ID: | CAAZKuFY80Ks34tfKRSqUP+JA2_UyZN9UVnkW5mrGgbreZbMRZw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sun, May 20, 2012 at 10:34 PM, Brendan Jurd <direvus(at)gmail(dot)com> wrote:
> What we don't do is *output* the 'T', but this is pretty easy to
> workaround, e.g., to_char(now(), 'YYYY-MM-DD"T"HH24:MI:SS'). The
> scope of actually wanting the 'T' is surely pretty minor?
>
> I'd be okay with just adding a note in the manual under Date/Time
> Output to the effect of "Note: ISO 8601 specifies the use of uppercase
> letter 'T' to separate the date and time. Postgres uses a space for
> improved readability, in line with other database systems and RFC
> 3339."
Yes, I believe you are quite right. My mistake, and I like your
suggestion, too, as it has successfully informed me of the most
accurate rendition of this.
--
fdr
From | Date | Subject | |
---|---|---|---|
Next Message | Benedikt Grundmann | 2012-05-21 07:57:06 | Re: Schema version management |
Previous Message | Brendan Jurd | 2012-05-21 05:34:26 | Re: External Open Standards |