Re: Range Types: empty ranges - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Range Types: empty ranges
Date
Msg-id AANLkTi=+23qFia_hZy=XAUUrC7eAe0SR8JbDCqf3VWU7@mail.gmail.com
Whole thread Raw
In response to Re: Range Types: empty ranges  (Jeff Davis <pgsql@j-davis.com>)
Responses Re: Range Types: empty ranges  (Jeff Davis <pgsql@j-davis.com>)
List pgsql-hackers
On Fri, Feb 11, 2011 at 3:03 PM, Jeff Davis <pgsql@j-davis.com> wrote:
> Well, there is a certain amount of localized clarity, I will agree with
> that. The complexity comes when you accidentally rely on some
> transformation which seems logically sound, but could result in a
> transient empty range, which then throws an error.

But by this argument you also need to support discontiguous ranges, don't you?

I mean, if you want to insist that A intersect B has to still be a
legal range, what about A union B?

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Jeff Davis
Date:
Subject: Re: Range Types: empty ranges
Next
From: Tom Lane
Date:
Subject: Re: ALTER EXTENSION UPGRADE, v3