| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Mark Rofail <markm(dot)rofail(at)gmail(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Alexander Korotkov <aekorotkov(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, David Steele <david(at)pgmasters(dot)net>, Stephen Frost <sfrost(at)snowman(dot)net> |
| Subject: | Re: GSoC 2017: Foreign Key Arrays |
| Date: | 2017-07-19 19:02:44 |
| Message-ID: | CA+TgmoZ3Ota88UeyDNeTN8LvbPmYwCVHK79zkqgPqEmuBYv3LA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jul 19, 2017 at 2:29 PM, Mark Rofail <markm(dot)rofail(at)gmail(dot)com> wrote:
> On Wed, Jul 19, 2017 at 7:28 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>>
>> Why do we have to solve that limitation?
>
> Since the regress test labled element_foreing_key fails now that I made the
> RI queries utilise @(anyarray, anyelement), that means it's not functioning
> as it is meant to be.
Well, if this is a new test introduced by the patch, you could also
just change the test. Off-hand, I'm not sure that it's very important
to make the case work where the types don't match between the
referenced table and the referencing table, which is what you seem to
be talking about here. But maybe I'm misunderstanding the situation.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2017-07-19 19:04:09 | Re: Something for the TODO list: deprecating abstime and friends |
| Previous Message | Robert Haas | 2017-07-19 19:00:21 | Re: Partition-wise join for join between (declaratively) partitioned tables |