pg.ddx.io pgsql-bugs@postgresql.org mailing list archivehelp / color / mirror / Atom feed
BUG #16309: Postgres's ISO 8601 date output is not compliant 2+ messages / 2 participants [nested] [flat]
* BUG #16309: Postgres's ISO 8601 date output is not compliant @ 2020-03-20 19:26 PG Bug reporting form <noreply@postgresql.org> 0 siblings, 1 reply; 2+ messages in thread From: PG Bug reporting form @ 2020-03-20 19:26 UTC (permalink / raw) To: pgsql-bugs@lists.postgresql.org; +Cc: cosmotic@gmail.com 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. ^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: BUG #16309: Postgres's ISO 8601 date output is not compliant @ 2020-03-20 20:09 David G. Johnston <david.g.johnston@gmail.com> parent: PG Bug reporting form <noreply@postgresql.org> 0 siblings, 0 replies; 2+ messages in thread From: David G. Johnston @ 2020-03-20 20:09 UTC (permalink / raw) To: cosmotic@gmail.com <cosmotic@gmail.com>; pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org> On Friday, March 20, 2020, PG Bug reporting form <noreply@postgresql.org> wrote: > 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. Not going to happen. The value in the column is the literal value to assign to the DateStyle GUC. If the output from postgres cannot be parsed by a strictly ISO 8601 parser, > than it should not be considered an ISO 8601 string. Fair point but its close enough for data interchange purposes. We, like most systems, are prepared to handle values with and without the âTâ. > A new style should be create that is actually ISO compliant. > Doesn't seem worthwhile. We conform to RFC3339 for our output and while we are stuck with a problematic name there is little apparent demand for including a strict ISO 8901 format output option since RFC3339 provides sufficient interoperability. And there is an unideal but doable alternative via to_char(). David J. ^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2020-03-20 20:09 UTC | newest] Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2020-03-20 19:26 BUG #16309: Postgres's ISO 8601 date output is not compliant PG Bug reporting form <noreply@postgresql.org> 2020-03-20 20:09 ` David G. Johnston <david.g.johnston@gmail.com>
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