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 <da...@fetter.org> http://fetter.org/ Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter Skype: davidfetter XMPP: david.fet...@gmail.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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers