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

From Robert Haas
Subject Re: [PATCH] Support for Array ELEMENT Foreign Keys
Date
Msg-id CA+TgmobHhFz3s4AOND3QQQP5mdy+EosDcNhsUHphEUVGYGuDMw@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] Support for Array ELEMENT Foreign Keys  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [PATCH] Support for Array ELEMENT Foreign Keys  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Fri, Oct 19, 2012 at 3:55 PM, Tom Lane <tgl@sss.pgh.pa.us> 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.

This is a little sneaky, but I presume you only get the grammar
conflict if you try to sneak the "each" or "element" or "each element"
or whatever-you-call-it designator in BEFORE the column name.  So what
about just putting it afterwards?  Something like this:

FOREIGN KEY (a, b BY ELEMENT) REFERENCES ...

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: [PATCH] Support for Array ELEMENT Foreign Keys
Next
From: Robert Haas
Date:
Subject: Re: [BUGS] BUG #7521: Cannot disable WAL log while using pg_dump