Re: [GENERAL] overlaps behaviour - ('2006-03-01'::TimeStamp, '2007-12-01'::TimeStamp) overlaps ('2007-12-01'::TimeStamp, 'Infinity'::TimeStamp)

2009-02-26 Thread Adrian Klaver
On Monday 23 February 2009 8:10:34 am Marek Lewczuk wrote: > Hello, > I can't find SQL definition for OVERLAPS operator so I don't know > whether following expression's result (false) is appropriate > behaviour: > select ('2006-03-01'::TimeStamp, '2007-12-01'::TimeStamp) overlaps > ('2007-12-01'::T

[GENERAL] overlaps behaviour - ('2006-03-01'::TimeStamp, '2007-12-01'::TimeStamp) overlaps ('2007-12-01'::TimeStamp, 'Infinity'::TimeStamp)

2009-02-26 Thread Marek Lewczuk
Hello, I can't find SQL definition for OVERLAPS operator so I don't know whether following expression's result (false) is appropriate behaviour: select ('2006-03-01'::TimeStamp, '2007-12-01'::TimeStamp) overlaps ('2007-12-01'::TimeStamp, 'Infinity'::TimeStamp) Can anyone confirm that ? In my under

Re: [GENERAL] OVERLAPS

2000-12-01 Thread Mike Castle
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)