| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | David Fetter <david(at)fetter(dot)org> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Brendan Jurd <direvus(at)gmail(dot)com>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: WIP: generalized index constraints |
| Date: | 2009-09-15 21:46:31 |
| Message-ID: | 1253051191.29243.107.camel@monkey-cat.sm.truviso.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 2009-09-15 at 14:42 -0700, Jeff Davis wrote:
> operator constraints
> operator exclusion constraints
> operator conflict constraints
> conflict operator constraints
> operator index constraints
> index constraints
> generalized index constraints
> something else?
Just to add a couple more permutations of Robert Haas's suggestions:
exclusion operator constraints
exclusive operator constraints
I also like those.
I think that using the word "operator" first makes it sound like the
operator is the thing being excluded, and adding "-based" makes it more
clear but it is too verbose.
Regards,
Jeff Davis
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-09-15 21:52:35 | Re: WIP: generalized index constraints |
| Previous Message | Jeff Davis | 2009-09-15 21:42:05 | Re: WIP: generalized index constraints |