Re: BUG #16747: Unexpected behaviour of the overlaps function

Поиск
Список
Период
Сортировка
От David G. Johnston
Тема Re: BUG #16747: Unexpected behaviour of the overlaps function
Дата
Msg-id CAKFQuwajaxxpf3j0eGO5vsMgBQUrs_SsJrGWhqqRUV3TuL0bCQ@mail.gmail.com
обсуждение исходный текст
Ответ на BUG #16747: Unexpected behaviour of the overlaps function  (PG Bug reporting form <noreply@postgresql.org>)
Список pgsql-bugs
Дерево обсуждения
On Thu, Nov 26, 2020 at 8:56 AM PG Bug reporting form <noreply@postgresql.org> wrote:
The following bug has been logged on the website:

Bug reference:      16747
Logged by:          Paul Luchyn
Email address:      ddiamondbbackk@gmail.com
PostgreSQL version: 11.8
Operating system:   Windows
Description:       

Hello!

I'm working with the "overlaps" function.
In my humble opinion it works incorrectly in one case.

Your examples perfectly match the documentation:

"Each time period is considered to represent the half-open interval start <= time < end, unless start and end are equal in which case it represents that single time instant. This means for instance that two time periods with only an endpoint in common do not overlap."

https://www.postgresql.org/docs/13/functions-datetime.html


And one more question: is there any other function which will do the trick
in the situation described in the last example?

Create an explicit range out of the timestamps and use one of the range operators/functions?

https://www.postgresql.org/docs/current/functions-range.html

David J.


В списке pgsql-bugs по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: BUG #16736: SCRAM authentication is not supported by this driver
Следующее
От: "Daniel Verite"
Дата:
Сообщение: Re: BUG #16736: SCRAM authentication is not supported by this driver