| From: | Alex Hunsaker <badalex(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Marco Nenciarini <marco(dot)nenciarini(at)2ndquadrant(dot)it>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Support for array_remove and array_replace functions |
| Date: | 2012-07-11 16:53:52 |
| Message-ID: | CAFaPBrQasSqBUbp1s85YwmKLJzWRRE1ie4D5_u4cgSkpfJLy3w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jul 11, 2012 at 9:54 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Marco Nenciarini <marco(dot)nenciarini(at)2ndquadrant(dot)it> writes:
>> Patch v3 attached.
>
> I'm looking at this patch now. The restriction of array_remove to
> one-dimensional arrays seems a bit annoying. I see the difficulty:
> if the input is multi-dimensional then removing some elements could
> lead to a non-rectangular array, which isn't supported. However,
> that could be dealt with by decreeing that the *result* is
> one-dimensional and of the necessary length, regardless of the
> dimensionality of the input.
Makes sense to me. +1
The other option ISTM is to replace removed entries with NULL-- which
I don't really like.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-07-11 17:00:34 | Re: Support for array_remove and array_replace functions |
| Previous Message | Tom Lane | 2012-07-11 15:54:50 | Re: Support for array_remove and array_replace functions |