RE: Datetime formatting - Mailing list pgsql-docs

From Kruus, Robert SPSA
Subject RE: Datetime formatting
Date
Msg-id YT2PR01MB50392D28125466B96F7AA4A6C6219@YT2PR01MB5039.CANPRD01.PROD.OUTLOOK.COM
Whole thread Raw
In response to Re: Datetime formatting  ("David G. Johnston" <david.g.johnston@gmail.com>)
List pgsql-docs

Sigh, I should just go home now…

 

From: David G. Johnston <david.g.johnston@gmail.com>
Sent: Thursday, January 27, 2022 10:26 AM
To: Kruus, Robert SPSA <Robert.Kruus@gov.sk.ca>; Pg Docs <pgsql-docs@lists.postgresql.org>
Subject: Re: Datetime formatting

 

WARNING: This message originated from a source that is not managed by SaskBuilds and Procurement, Information Technology Division. Do not visit links or open attachments unless you trust the sender's email ID and ensure it is not a spam/phishing email.

 

On Thu, Jan 27, 2022 at 9:13 AM PG Doc comments form <noreply@postgresql.org> wrote:


Page: https://www.postgresql.org/docs/14/datatype-datetime.html

Might want to make a note that the current behavior does not match the
latest standard, but does match previous editions and/or RFC 3339.

 

We have such a note - it even gets printed in a big blue box.

 

"""

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, as shown above. This is for readability and for consistency with RFC 3339 as well as some other database systems.

"""

 

David J.

 

pgsql-docs by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: Datetime formatting
Next
From: PG Doc comments form
Date:
Subject: documentation typo