Re: operator exclusion constraints [was: generalized index constraints]
Robert Haas <robertmhaas@gmail.com>
From: Robert Haas <robertmhaas@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Jeff Davis <pgsql@j-davis.com>, Peter Eisentraut <peter_e@gmx.net>, pgsql-hackers@postgresql.org
Date: 2009-09-27T18:23:38Z
Lists: pgsql-hackers
On Sun, Sep 27, 2009 at 1:08 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote: > 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) I don't like that as well as USING OPERATOR, but I like it far better than any of the single-word choices, so maybe it's a reasonable compromise. ...Robert