Re: operator exclusion constraints - Mailing list pgsql-hackers

From Jeff Davis
Subject Re: operator exclusion constraints
Date
Msg-id 1257548615.28470.269.camel@monkey-cat.sm.truviso.com
Whole thread Raw
In response to Re: operator exclusion constraints  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: operator exclusion constraints
List pgsql-hackers
On Fri, 2009-11-06 at 14:59 -0500, Tom Lane wrote:
> If we restrict this thing to being a table constraint, not a column
> constraint, it seems like the issue might go away (and in fact I think
> you might not even need col_name_keyword).

I never enabled the syntax for column constraints, so it was always a
part of ConstraintElem.

To make sure I understand what you're saying, you think that:

CREATE TABLE foo
( exclusion int, EXCLUSION (exclusion CHECK WITH =)
);

should work? It's not ambiguous, but I'm not an expert on the grammar,
so I don't immediately know a non-invasive way to express that.

Regards,Jeff Davis



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Specific names for plpgsql variable-resolution control options?
Next
From: Marc Munro
Date:
Subject: Quoting oddities when defining operators in postgres 8.3