Re: 9.6 Feature help requested: Inclusion Constraints - Mailing list pgsql-hackers

From Robert Haas
Subject Re: 9.6 Feature help requested: Inclusion Constraints
Date
Msg-id CA+TgmoZKz0a1KoiD1rQRB0xpXja6rLzpeEV85GNu3ra0UCtppg@mail.gmail.com
Whole thread Raw
In response to Re: 9.6 Feature help requested: Inclusion Constraints  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
On Tue, Feb 10, 2015 at 9:47 PM, Peter Eisentraut <peter_e@gmx.net> wrote:
> On 2/9/15 3:12 AM, Jeff Davis wrote:
>> On Sat, 2015-02-07 at 16:08 -0800, Jeff Davis wrote:
>>> I believe Inclusion Constraints will be important for postgres.
>>
>> I forgot to credit Darren Duncan with the name of this feature:
>>
>> http://www.postgresql.org/message-id/4F8BB9B0.5090708@darrenduncan.net
>
> I think it would be confusing to name something inclusion constraint
> that is not somehow the opposite of an exclusion constraint.

It sorta is.  UNIQUE is to exclusion constrant as FOREIGN KEY is to
inclusion constraint.

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



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: reducing our reliance on MD5
Next
From: Magnus Hagander
Date:
Subject: Re: reducing our reliance on MD5