From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [PATCH] Support for Array ELEMENT Foreign Keys |
Date: | 2012-10-19 21:29:49 |
Message-ID: | 5081C64D.6000008@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 10/19/2012 04:40 PM, Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2012-10-19 22:05:15 | Re: assertion failure w/extended query protocol |
Previous Message | Peter Geoghegan | 2012-10-19 21:22:11 | Re: Deprecating RULES |