| From: | Mark Rofail <markm(dot)rofail(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Alexander Korotkov <aekorotkov(at)gmail(dot)com>, Robert Haas <robertmhaas(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-12 12:30:21 |
| Message-ID: | CAJvoCuusYZvvLKY=5FuipynY8VTC86Q_6AM=cw4C+WPgjkwytA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jul 12, 2017 at 12:53 AM, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
wrote:
>
> We have one opclass for each type combination -- int4 to int2, int4 to
> int4, int4 to int8, etc. You just need to add the new strategy to all
> the opclasses.
>
Can you clarify this solution ? I think another solution would be external
casting
BTW now that we've gone through this a little further, it's starting to
> look like a mistake to me to use the same @> operator for (anyarray,
> anyelement) than we use for (anyarray, anyarray).
I agree. Changed to @>>
Best Regards,
Mark Rofail
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2017-07-12 12:34:29 | DSA on 32 bit systems |
| Previous Message | Sandeep Thakkar | 2017-07-12 12:19:09 | pl/perl extension fails on Windows |