Re: operator exclusion constraints [was: generalized index constraints] - Mailing list pgsql-hackers

From Tom Lane
Subject Re: operator exclusion constraints [was: generalized index constraints]
Date
Msg-id 25486.1254071300@sss.pgh.pa.us
Whole thread Raw
In response to Re: operator exclusion constraints [was: generalized index constraints]  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: operator exclusion constraints [was: generalized index constraints]
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> On Wed, Sep 23, 2009 at 1:47 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> I think that USING is just about as content-free as WITH in this
>> particular example --- it doesn't give you any hint about what the
>> purpose of the operator is.

> USING might be just as content-free as WITH, but USING OPERATOR seems
> clearly better, at least IMO.

It's not enough better to justify the conflict with USING opclass, IMO.

An idea that just struck me is CHECK WITH, ie
EXCLUSION (expr CHECK WITH operator)
        regards, tom lane


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: operator exclusion constraints [was: generalized index constraints]
Next
From: Petr Jelinek
Date:
Subject: Re: GRANT ON ALL IN schema