| From: | Reg Me Please <regmeplease(at)gmail(dot)com> |
|---|---|
| To: | Jeff Davis <pgsql(at)j-davis(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: A better BETWEEN for DATEs, TIMEs and TIMESTAMPs? |
| Date: | 2009-01-14 21:45:20 |
| Message-ID: | 200901142245.20610.regmeplease@gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wednesday 14 January 2009 22:38:07 Jeff Davis wrote:
> 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
Jeff, I'll give your implementation a try and possibly a look to the code
itself.
I thought that was not just my personal opinion, though.
--
Fahrbahn ist ein graues Band
weisse Streifen, grüner Rand
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Madison Kelly | 2009-01-14 21:50:22 | Re: Odd duplicate database |
| Previous Message | Jeff Davis | 2009-01-14 21:38:07 | Re: A better BETWEEN for DATEs, TIMEs and TIMESTAMPs? |