Re: [HACKERS] GSoC 2017: Foreign Key Arrays
| От | Robert Haas |
|---|---|
| Тема | Re: [HACKERS] GSoC 2017: Foreign Key Arrays |
| Дата | |
| Msg-id | CA+TgmoZ3Ota88UeyDNeTN8LvbPmYwCVHK79zkqgPqEmuBYv3LA@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: [HACKERS] GSoC 2017: Foreign Key Arrays (Mark Rofail <markm.rofail@gmail.com>) |
| Список | pgsql-hackers |
On Wed, Jul 19, 2017 at 2:29 PM, Mark Rofail <markm.rofail@gmail.com> wrote: > On Wed, Jul 19, 2017 at 7:28 PM, Robert Haas <robertmhaas@gmail.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
В списке pgsql-hackers по дате отправления: