| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Marco Nenciarini <marco(dot)nenciarini(at)2ndquadrant(dot)it>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [PATCH] Support for Array ELEMENT Foreign Keys |
| Date: | 2012-10-19 20:21:46 |
| Message-ID: | CA+TgmobHhFz3s4AOND3QQQP5mdy+EosDcNhsUHphEUVGYGuDMw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Oct 19, 2012 at 3:55 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2012-10-19 20:25:07 | Re: BUG #7521: Cannot disable WAL log while using pg_dump |
| Previous Message | Andrew Dunstan | 2012-10-19 20:06:43 | Re: [PATCH] Support for Array ELEMENT Foreign Keys |