| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Kacper Kuras <kacperkuras(at)hotmail(dot)com> |
| Cc: | "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:22:57 |
| Message-ID: | aq1lYd1pbqjniS6P@momjian.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Fri, Sep 18, 2026 at 04:09:39PM +0000, Kacper Kuras wrote:
> > 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.
How about this patch?
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
Do not let urgent matters crowd out time for investment in the future.
| Attachment | Content-Type | Size |
|---|---|---|
| ISO8601.diff | text/x-diff | 734 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kacper Kuras | 2026-09-18 16:34:05 | Re: 8.5.1. Date/Time Input |
| Previous Message | Kacper Kuras | 2026-09-18 16:09:39 | Re: 8.5.1. Date/Time Input |