overlaps() bug?

From: jeff_patterson(at)agilent(dot)com
To: pgsql-general(at)postgresql(dot)org
Subject: overlaps() bug?
Date: 2002-02-12 18:54:17
Message-ID: 08E9E30FCA2CD5119BEA0090274066DF01D312FE@axcs16.cos.agilent.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Note the third row in the query result below is in error. The four hour
interval
(2300UTC - 0300UTC) does not overlap the interval 1530UTC-1627UTC). Is this
a bug? It would be cool if timetz (or time) datatypes were to wrap properly
across day boundaries (i.e. if start time < stop time then assume start time
is day before) but at the very least, the overlaps functions should not lie
to you!

Jeff Patterson

swl=# select freq,start,stop from sched where freq = '7200' and
swl-# overlaps(timetz '15:30UTC',timetz '16:27UTC',start,stop);
freq | start | stop
------+-------------+-------------
7200 | 15:30:00+00 | 16:27:00+00
7200 | 15:00:00+00 | 17:00:00+00
7200 | 23:00:00+00 | 03:00:00+00
7200 | 21:00:00+00 | 16:00:00+00
7200 | 16:00:00+00 | 19:00:00+00
7200 | 15:00:00+00 | 16:00:00+00
7200 | 20:00:00+00 | 16:00:00+00
7200 | 02:00:00+00 | 16:30:00+00

Attachment Content-Type Size
Jeff Patterson (E-mail).vcf application/octet-stream 559 bytes

Browse pgsql-general by date

  From Date Subject
Next Message Chris Gamache 2002-02-12 20:02:32 Re: 7.1.3 : copy from stdin is very slow!
Previous Message Bruce Momjian 2002-02-12 18:27:03 Re: [HACKERS] Feature enhancement request : use of libgda