Re: BUG #18445: date_part / extract range for hours do not match documentation - Mailing list pgsql-bugs

From David G. Johnston
Subject Re: BUG #18445: date_part / extract range for hours do not match documentation
Date
Msg-id CAKFQuwbzoqKWb9n86sTaOuOp_0_WUfGC0vLHV0kJkyDpHSyHaQ@mail.gmail.com
Whole thread Raw
In response to Re: BUG #18445: date_part / extract range for hours do not match documentation  (Marek Läll <lall.marek@gmail.com>)
List pgsql-bugs


On Fri, Apr 26, 2024, 12:28 Marek Läll <lall.marek@gmail.com> wrote:
We tend not to introduce breaking changes if the only motivation is to be consistent.
 
Other mistakes are minor, but why is time '24:00:00' allowed, and it's actually 00:00:00 of the next day, that's something I'd like to read a well-argued design decision.
It's like months 1 through 12, and just in case, we also allow month 13, which represents January of the next year. But month 14 is not allowed, which could represent February of the next year.
Could you share the rationale behind this decision?

It can be easier to construct "< date 24:00:00" to represent until the end of date rather than producing "< date+1 00:00:00"

David J.

pgsql-bugs by date:

Previous
From: Marek Läll
Date:
Subject: Re: BUG #18445: date_part / extract range for hours do not match documentation
Next
From: Tom Lane
Date:
Subject: Re: BUG #18445: date_part / extract range for hours do not match documentation