A Nit RE overlaps
От | Ian Harding |
---|---|
Тема | A Nit RE overlaps |
Дата | |
Msg-id | sc3c0f5f.062@mail.tpchd.org обсуждение исходный текст |
Ответы |
Re: A Nit RE overlaps
|
Список | pgsql-general |
I love overlaps() but I would love it more if it had a overlaps(date, date, date, date) variant that would work like this: select overlaps( cast('01/01/2002' as date), cast('6/1/2002' as date), cast('6/1/2002' as date), cast('12/31/2002' as date) ); overlaps ---------- t (1 row) As it is, it returns false. To me if the first interval ends at a point in time and the other begins at the same point,they overlap. This is splitting hairs with a timestamp, but not with a date. Am I the only person who feels thisway? Is there a way to use overlaps as above and make it return true? In my twisted little world, a null date would be OK too and would indicate the beginning or end of time. i.e. select overlaps( cast('01/01/2002' as date), cast(null as date), cast('6/1/2002' as date), cast('12/31/2002' as date) ); would return overlaps ---------- t (1 row) since the first interval goes on forever. I know that is a bad use of nulls in terms of its meaning as 'unknown' so I guessthat's a hack I will have to continue doing myself. But I am still interested in knowing if there is any interest ina version of overlaps that considers events that occur at the same point in time to be overlapping. Ian A. Harding Programmer/Analyst II Tacoma-Pierce County Health Department (253) 798-3549 mailto: iharding@tpchd.org
В списке pgsql-general по дате отправления: