Re: Support for array_remove and array_replace functions

Поиск
Список
Период
Сортировка
Искать
От
Tom Lane
Тема
Re: Support for array_remove and array_replace functions
Дата
Msg-id
15405.1342030015@sss.pgh.pa.us
Ответ на
Список
Дерево обсуждения
Support for array_remove and array_replace functions Marco Nenciarini <marco.nenciarini@2ndquadrant.it>
Re: Support for array_remove and array_replace functions Alex Hunsaker <badalex@gmail.com>
Re: Support for array_remove and array_replace functions Marco Nenciarini <marco.nenciarini@2ndquadrant.it>
Re: Support for array_remove and array_replace functions Tom Lane <tgl@sss.pgh.pa.us>
Re: Support for array_remove and array_replace functions Tom Lane <tgl@sss.pgh.pa.us>
Re: Support for array_remove and array_replace functions Alex Hunsaker <badalex@gmail.com>
Re: Support for array_remove and array_replace functions Tom Lane <tgl@sss.pgh.pa.us>
Re: Support for array_remove and array_replace functions Robert Haas <robertmhaas@gmail.com>
Re: Support for array_remove and array_replace functions Alex Hunsaker <badalex@gmail.com>
Marco Nenciarini  writes:
> Patch v3 attached.

Applied with mostly-but-not-entirely cosmetic adjustments.

I left array_remove throwing error for multi-dimensional arrays for
the moment, because I realized that changing the dimensionality as
I suggested would conflict with the optimization to return the original
array if there were no matches.  I don't think we'd want the definition
to read "multidimensional arrays are changed to one dimension, but only
if at least one element is removed" --- that's getting a little too
weird.  If anyone's really hot to make it work on multi-D arrays, we
could consider disabling that optimization; it's not clear to me that
it's worth a lot.  But for now I'm willing to stick with the
throw-an-error approach.
		regards, tom lane

В списке pgsql-hackers по дате отправления
От: Merlin Moncure
Дата:
Сообщение: Re: Schema version management
От: Josh Berkus
Дата:
FAQ