| From: | PG Bug reporting form <noreply(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Cc: | cosmotic(at)gmail(dot)com |
| Subject: | BUG #16309: Postgres's ISO 8601 date output is not compliant |
| Date: | 2020-03-20 19:26:18 |
| Message-ID: | 16309-624405df40e39b05@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 16309
Logged by: Charlie Hayes
Email address: cosmotic(at)gmail(dot)com
PostgreSQL version: 11.6
Operating system: docker
Description:
Per Postgres's own documentation, ISO 8601 date output is NOT compliant
(Despite what the style name suggests):
https://www.postgresql.org/docs/12/datatype-datetime.html#DATATYPE-DATETIME-OUTPUT
The existing "Style Specification" name should be changed to something other
than ISO since it is NOT ISO compliant.
If the output from postgres cannot be parsed by a strictly ISO 8601 parser,
than it should not be considered an ISO 8601 string.
A new style should be create that is actually ISO compliant.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2020-03-20 20:09:23 | Re: BUG #16309: Postgres's ISO 8601 date output is not compliant |
| Previous Message | Robert Haas | 2020-03-20 02:21:53 | Re: BUG #16302: too many range table entries - when count partition table(65538 childs) |