From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Joshua Tolley <eggyknap(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jeff Davis <pgsql(at)j-davis(dot)com>, David Fetter <david(at)fetter(dot)org>, 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-16 15:04:14 |
Message-ID: | 603c8f070909160804s71145c1cn73d797973884ac26@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Sep 15, 2009 at 7:02 PM, Joshua Tolley <eggyknap(at)gmail(dot)com> wrote:
> On Tue, Sep 15, 2009 at 05:52:35PM -0400, Tom Lane wrote:
>> Jeff Davis <pgsql(at)j-davis(dot)com> writes:
>> > 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
>>
>> To my ear, "operator exclusion constraints" or "exclusive operator
>> constraints" seem reasonable; the other permutations of that phrase
>> simply aren't good English.
>
> I was having a hard time coming up with a name that was adequately
> short-and-sweet, and still conveyed the idea of both "operator" and "index",
> which seems important so as to designate between these and the constraints
> we've had all along. Perhaps "indexed operator constraints"?
Really I suppose they are indexed operator exclusion constraints, but
that may be too wordy.
...Robert
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2009-09-16 15:36:22 | Re: Linux LSB init script |
Previous Message | Steve Prentice | 2009-09-16 14:19:25 | Re: PATCH: make plpgsql IN args mutable (v1) [REVIEW] |