Re: GSoC 2017: Foreign Key Arrays

From: Mark Rofail <markm(dot)rofail(at)gmail(dot)com>
To: Robert Haas <robertmhaas(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 18:29:13
Message-ID: CAJvoCuuEGWppiS5_PnX8D0bBH_TqfeEpKcc3eOSnCq-x9qKukw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2017-07-19 18:31:06 Re: Using non-sequential timelines in order to help with possible collisions
Previous Message Tom Lane 2017-07-19 18:23:52 Re: PG10b2: column-list UPDATE syntax fails with single column