OVERLAPS

Lists: pgsql-general
From: "Alex Bolenok" <abolen(at)chat(dot)ru>
To: <pgsql-general(at)postgresql(dot)org>
Subject: OVERLAPS
Date: 2000-11-30 13:22:20
Message-ID: 000d01c05ad0$9ae76fd0$0e02a8c0@artey.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-general

Hello all,

Here is the result I get when trying to use OVERLAPS function:

peroon=# SELECT OVERLAPS('yesterday', 'today', 'today', 'tomorrow');
ERROR: parser: parse error at or near "overlaps"

What am I doing wrong? Is there any way to make this function work?

Alex Bolenok.


From: Mike Castle <dalgoda(at)ix(dot)netcom(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: OVERLAPS
Date: 2000-12-02 01:05:58
Message-ID: 20001201190558.B12425@thune.mrc-home.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-general

On Thu, Nov 30, 2000 at 04:22:20PM +0300, Alex Bolenok wrote:
> peroon=# SELECT OVERLAPS('yesterday', 'today', 'today', 'tomorrow');
> ERROR: parser: parse error at or near "overlaps"

Try using it as an operator instead of a function:

test=# select ('yesterday'::timestamp, 'today'::timestamp) overlaps
('today'::timestamp, 'tomorrow'::timestamp);
overlaps
----------
f
(1 row)

> What am I doing wrong? Is there any way to make this function work?

Is the parser getting confused when it shouldn't (ie, if the functions were
called something beside "OVERLAPS" would it then work)?

mrc
--
Mike Castle Life is like a clock: You can work constantly
dalgoda(at)ix(dot)netcom(dot)com and be right all the time, or not work at all
www.netcom.com/~dalgoda/ and be right at least twice a day. -- mrc
We are all of us living in the shadow of Manhattan. -- Watchmen