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
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
On 2023-11-15 15:46 +0100, Tom Lane wrote:
> Erik Wienhold writes:
> > On 2023-11-15 12:53 +0100, Peter Eisentraut wrote:
> >> I think we should reframe "ISO" to mean "ISO 9075" and remove all claims of
> >> alignment with ISO 8601 and RFC 3339.
>
> > Agree. So just list the example inputs witho
Erik Wienhold writes:
> On 2023-11-15 12:53 +0100, Peter Eisentraut wrote:
>> I think we should reframe "ISO" to mean "ISO 9075" and remove all claims of
>> alignment with ISO 8601 and RFC 3339.
> Agree. So just list the example inputs without any reference to a
> particular standard, except for
On 2023-11-15 12:53 +0100, Peter Eisentraut wrote:
> On 15.11.23 09:37, Erik Wienhold wrote:
> > On 2023-11-15 08:16 +0100, Peter Eisentraut wrote:
> > > The SQL standard does not refer to ISO 8601 to define date formats, it has
> > > its own definitions. In fact, PostgreSQL implements more date f
On 15.11.23 09:37, Erik Wienhold wrote:
On 2023-11-15 08:16 +0100, Peter Eisentraut wrote:
The SQL standard does not refer to ISO 8601 to define date formats, it has
its own definitions. In fact, PostgreSQL implements more date formats than
the SQL standard requires.
Really? Then what does t
On 2023-11-15 08:16 +0100, Peter Eisentraut wrote:
> The SQL standard does not refer to ISO 8601 to define date formats, it has
> its own definitions. In fact, PostgreSQL implements more date formats than
> the SQL standard requires.
Really? Then what does the standard mean with section "Definit
On 14.11.23 19:21, Erik Wienhold wrote:
I did not say that occurrences of "ISO 8601" should be replaced with
"RFC 3339". Just that the docs should have a cautionary note about the
SQL standard using a subset of ISO 8601 and that Postgres does not
implement (at the moment) all of its date formats
On 2023-11-13 17:23 +0100, Tom Lane wrote:
> Erik Wienhold writes:
> > On 2023-11-13 15:24 +0100, Erik Wienhold wrote:
> >> I also noticed that when people say "ISO 8601" they usually mean RFC
> >> 3389 or some subset of ISO 8601.
>
> > Forgot this fine visualization of the differences:
> > https
Erik Wienhold writes:
> On 2023-11-13 15:24 +0100, Erik Wienhold wrote:
>> I also noticed that when people say "ISO 8601" they usually mean RFC
>> 3389 or some subset of ISO 8601.
> Forgot this fine visualization of the differences:
> https://ijmacd.github.io/rfc3339-iso8601/
I'm inclined not to
On 2023-11-13 15:24 +0100, Erik Wienhold wrote:
> I also noticed that when people say "ISO 8601" they usually mean RFC
> 3389 or some subset of ISO 8601.
Forgot this fine visualization of the differences:
https://ijmacd.github.io/rfc3339-iso8601/
--
Erik
On 2023-11-13 12:27 +0100, Roman Frołow wrote:
> It seems I was wrong.
> Now T is mandatory in ISO8601 and from RFC3339 it seems this requirement is
> relaxed.
Right. RFC 3339 is from 2002 and it references ISO 8601:1988 where T
was optional. (Until today I didn't even know about the 2019 editio
It seems I was wrong.
Now T is mandatory in ISO8601 and from RFC3339 it seems this requirement is
relaxed.
-
https://stackoverflow.com/questions/9531524/in-an-iso-8601-date-is-the-t-character-mandatory#comment89287877_34006233
-
https://en.m.wikipedia.org/wiki/ISO_8601#Combined_date_and_time_repre
So what should be changed?
postgresql docs say that it is consistent with rfc3339 using space.
Also look at this:
> In addition, an uppercase "T" character MUST be used to separate date and
time
https://validator.w3.org/feed/docs/error/InvalidRFC3339Date.html
I would say that postgresql is not
On 2023-11-11 23:45 +0100, PG Doc comments form wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/16/git.html
> Description:
>
> >ISO 8601 specifies the use of uppercase letter T to separate the date and
> time. PostgreSQL accep
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/16/git.html
Description:
>ISO 8601 specifies the use of uppercase letter T to separate the date and
time. PostgreSQL accepts that format on input, but on output it uses a space
rather than T,
16 matches
Mail list logo
