| From: | Kacper Kuras <kacperkuras(at)hotmail(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us>, "pgsql-docs(at)lists(dot)postgresql(dot)org" <pgsql-docs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: 8.5.1. Date/Time Input |
| Date: | 2026-09-18 16:09:39 |
| Message-ID: | VI0P193MB31116A84F36E1434E1D4B9FABF872@VI0P193MB3111.EURP193.PROD.OUTLOOK.COM |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
> The "agreement between the sender and the receiver" makes it seem we
> don't need to document that we don't support signs on the years.
Agreement needs each side to state its terms, though, and PostgreSQL
states its terms in the documentation. It already does for the other
by-agreement range: ISO 8601 leaves years before 1583 to agreement,
and B.6 settles them - proleptic Gregorian for all dates - if you
think to look in an appendix on calendar history. For a leading sign
there is only B.1's tokenizing rule, "either a numeric time zone or
a special field", which says nothing about years. So a client finds
out by trying: -0001-01-02, the wiki's own 2 BC, is refused as
invalid input syntax, and +10000-01-02 as a time zone displacement.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2026-09-18 16:22:57 | Re: 8.5.1. Date/Time Input |
| Previous Message | Bruce Momjian | 2026-09-18 15:48:53 | Re: 8.5.1. Date/Time Input |