Re: [PATCH] Support for Array ELEMENT Foreign Keys - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: [PATCH] Support for Array ELEMENT Foreign Keys
Date
Msg-id 5081C64D.6000008@dunslane.net
Whole thread Raw
In response to Re: [PATCH] Support for Array ELEMENT Foreign Keys  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 10/19/2012 04:40 PM, Tom Lane wrote:
> Andrew Dunstan <andrew@dunslane.net> writes:
>> On 10/19/2012 03:55 PM, Tom Lane wrote:
>>> That doesn't get us any closer to having a working column-constraint
>>> syntax unfortunately, because EACH is not a reserved word either
>>> so "EACH ELEMENT REFERENCES" still isn't gonna work.  I'm getting
>>> more willing to give up on having a column-constraint form of this.
>> "ALL" is a fully reserved keyword. Could we do something like "ALL
>> ELEMENTS"?
> [ experiments... ]  bison is happy with "ALL ELEMENTS REFERENCES ..."
> as a column constraint, but from the standpoint of English grammar
> it's kinda sucky.  "ANY ELEMENT REFERENCES ..." would be fine but
> that's not the case we're implementing now.
>
>             

Well, we could add "REFERENCE" as a non-reserved keyword. I agree it's 
not ideal.

cheers

andrew




pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: Deprecating RULES
Next
From: Tom Lane
Date:
Subject: Re: assertion failure w/extended query protocol