Re: A better BETWEEN for DATEs, TIMEs and TIMESTAMPs?

From: Jeff Davis <pgsql(at)j-davis(dot)com>
To: Reg Me Please <regmeplease(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: A better BETWEEN for DATEs, TIMEs and TIMESTAMPs?
Date: 2009-01-14 21:38:07
Message-ID: 1231969087.32625.123.camel@dell.linuxdev.us.dell.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, 2009-01-14 at 13:35 -0800, Jeff Davis wrote:
> I think the best solution is to make first-class interval types (for
> time as well as other types). Those intervals can then have operators
> like "contains" and "contained by" which would solve your problem.
>
> Additionally, it would allow lots of other interesting operations, like
> overlaps and intersects.

I wrote such an interval type here, called "period" (to avoid confusion
with the SQL INTERVAL type):

http://pgfoundry.org/projects/temporal

Regards,
Jeff Davis

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Reg Me Please 2009-01-14 21:45:20 Re: A better BETWEEN for DATEs, TIMEs and TIMESTAMPs?
Previous Message Tom Lane 2009-01-14 21:36:43 Re: Odd duplicate database