From: | Erik Wienhold <ewie(at)ewie(dot)name> |
---|---|
To: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Roman Frołow <rofrol(at)gmail(dot)com>, pgsql-docs(at)lists(dot)postgresql(dot)org |
Subject: | Re: T is a mandatory date time separator in RFC3339 but documentation states differently |
Date: | 2023-11-20 13:30:16 |
Message-ID: | 5aumqtocm4auhragpanvy36u33xsv2zueacfq35klxxc35eeaf@oomrqo7mhg6l |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On 2023-11-20 08:14 +0100, Peter Eisentraut wrote:
> On 19.11.23 21:34, Erik Wienhold wrote:
> > * Making explicit references to ISO 8601:2004 where section numbers are
> > referenced. Mostly in source comments but also a couple of places in
> > the docs. This is about avoiding confusion as ISO 8601:2019 has been
> > published since then, with different section numbers[1]. The pre-2004
> > editions also have different section numbers. References to general
> > ISO 8601 concepts (e.g. week numbers) are left unchanged because those
> > are not tied to any particular edition.
>
> Maybe we should change the references to the 2019 edition instead?
I wouldn't do that without knowing the full text of the standard. Maybe
I can eyeball which 2004 sections map to 2019 sections but I wouldn't be
confident in that.
Also 8601:2019 removed 24:00 as midnight for some reason but it is
allowed again with an ammendment from 2022. Not sure what else changed
besides the "main changes" summarized in the foreword of [1]. And I
can't find the 2022 ammendment on iso.org.
[1] https://www.iso.org/obp/ui/en/#iso:std:iso:8601:-1:ed-1:v1:en
--
Erik
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2023-11-21 02:04:12 | Re: SELECT ... FOR UPDATE OF clause documentation implies use of table_names rather than aliases |
Previous Message | Peter Eisentraut | 2023-11-20 07:14:50 | Re: T is a mandatory date time separator in RFC3339 but documentation states differently |