| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCH] Support for Array ELEMENT Foreign Keys |
| Date: | 2012-10-19 20:40:43 |
| Message-ID: | 8635.1350679243@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-10-19 20:48:41 | Re: [PATCH] Support for Array ELEMENT Foreign Keys |
| Previous Message | Robert Haas | 2012-10-19 20:25:07 | Re: BUG #7521: Cannot disable WAL log while using pg_dump |