| From: | Brendan Jurd <direvus(at)gmail(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Daniel Farina <daniel(at)heroku(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: External Open Standards |
| Date: | 2012-05-24 03:50:23 |
| Message-ID: | CADxJZo1ckOPsxo1jqd9=-W-3Rvp5MWz2oT8e3AGtO3wE5Ez2jw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 24 May 2012 05:30, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> On mån, 2012-05-21 at 15:34 +1000, Brendan Jurd wrote:
>> 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."
>
> But that is wrong. We use the space because SQL says so. The reason we
> have all those other formats is for readability or consistency or some
> secondary standard. But the format of the ISO format is exactly what
> the SQL standard says, without any other considerations.
>
Did you miss my follow-on message on this thread? You are responding
to a message that has been superceded. I saw what you wrote earlier,
and updated my suggestions for the docs 2 days ago.
Please see
Cheers,
BJ
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Korotkov | 2012-05-24 04:04:12 | Re: Patch: add conversion from pg_wchar to multibyte |
| Previous Message | Tom Lane | 2012-05-23 22:46:53 | Re: WIP: parameterized function scan |