| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Brendan Jurd <direvus(at)gmail(dot)com>, 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-23 19:41:48 |
| Message-ID: | 10275.1337802108@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> On mn, 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.
Well, in that case we really need to rewrite the text to not look like
it's citing 8601 as the primary reference. We could replace the <note>
I added with something to the effect that the SQL standard matches 8601
except for not using 'T'.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kohei KaiGai | 2012-05-23 19:45:52 | Re: [RFC] Interface of Row Level Security |
| Previous Message | Peter Eisentraut | 2012-05-23 19:36:19 | should postgres -C print units? |