From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Alex Hunsaker <badalex(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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 17:40:50 |
Message-ID: | EB4DDD52-8FFE-4CE7-92AD-7826EFB4CC59@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Jul 11, 2012, at 11:53 AM, Alex Hunsaker <badalex(at)gmail(dot)com> wrote:
> 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
+1 from me, too.
...Robert
From | Date | Subject | |
---|---|---|---|
Next Message | Merlin Moncure | 2012-07-11 18:01:54 | Re: Schema version management |
Previous Message | Tom Lane | 2012-07-11 17:00:34 | Re: Support for array_remove and array_replace functions |