Re: WIP: RangeTypes

From: David Fetter <david(at)fetter(dot)org>
To: Jeff Davis <pgsql(at)j-davis(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: WIP: RangeTypes
Date: 2011-01-17 21:23:31
Message-ID: 20110117212331.GE18561@fetter.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jan 17, 2011 at 01:09:26PM -0800, Jeff Davis wrote:
> When defining generic range functions, there is quite a bit of extra
> complexity needed to handle special cases.
>
> The special cases are due to:
> * empty ranges
> * ranges with infinite boundaries
> * ranges with NULL boundaries
> * ranges with exclusive bounds (e.g. "(" or ")").
>
> Infinite bounds, and exclusive bounds can both be handled somewhat
> reasonably, and the complexity can be somewhat hidden. Empty ranges
> are a special case, but can be handled at the top of the generic
> function in a straightforward way.
>
> NULL bounds, however, have been causing me a little frustration.
> [Explanation and illustrations].

In that case, let's leave them out for this cut.

Cheers,
David.
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: david(dot)fetter(at)gmail(dot)com
iCal: webcal://www.tripit.com/feed/ical/people/david74/tripit.ics

Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Dan Ports 2011-01-17 21:26:06 Re: SSI patch version 12
Previous Message Noah Misch 2011-01-17 21:13:12 Re: texteq/byteaeq: avoid detoast [REVIEW]