| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Jeff Davis <pgsql(at)j-davis(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: 9.6 Feature help requested: Inclusion Constraints |
| Date: | 2015-02-11 14:29:09 |
| Message-ID: | CA+TgmoZKz0a1KoiD1rQRB0xpXja6rLzpeEV85GNu3ra0UCtppg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Feb 10, 2015 at 9:47 PM, Peter Eisentraut <peter_e(at)gmx(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2015-02-11 14:34:52 | Re: reducing our reliance on MD5 |
| Previous Message | Robert Haas | 2015-02-11 14:26:23 | Re: reducing our reliance on MD5 |