From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: cosmotic@gmail.com
Subject: BUG #16309: Postgres's ISO 8601 date output is not compliant
Date: Fri, 20 Mar 2020 19:26:18 +0000
Message-ID: <16309-624405df40e39b05@postgresql.org> (raw)
The following bug has been logged on the website:
Bug reference: 16309
Logged by: Charlie Hayes
Email address: cosmotic@gmail.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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-bugs@postgresql.org
Cc: noreply@postgresql.org, cosmotic@gmail.com
Subject: Re: BUG #16309: Postgres's ISO 8601 date output is not compliant
In-Reply-To: <16309-624405df40e39b05@postgresql.org>
References: <16309-624405df40e39b05@postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox