Re: GSoC 2017: Foreign Key Arrays

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 17:28:25
Message-ID: CA+Tgmobnga_huBCeAT1uCuYDNVVUPXB8VfRrzvQpaN0QxLpUHA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Jul 19, 2017 at 8:08 AM, Mark Rofail <markm(dot)rofail(at)gmail(dot)com> wrote:
> To summarise, the options we have to solve the limitation of the @>(anyarray
> , anyelement) where it produces the following error: operator does not
> exist: integer[] @> smallint

Why do we have to solve that limitation?

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2017-07-19 17:29:17 Re: Cache lookup errors with functions manipulation object addresses
Previous Message Robert Haas 2017-07-19 17:23:18 Re: Something for the TODO list: deprecating abstime and friends