Re: jsonb concatenate operator's semantics seem questionable

Поиск
Список
Период
Сортировка
От Catalin Iacob
Тема Re: jsonb concatenate operator's semantics seem questionable
Дата
Msg-id CAHg_5go7BAE9dhyCtM5E1Q6F8U4xBXJAoMhvXnfzsaBhV3bfDg@mail.gmail.com
обсуждение исходный текст
Ответ на Re: jsonb concatenate operator's semantics seem questionable  (Andrew Dunstan <andrew@dunslane.net>)
Ответы Re: jsonb concatenate operator's semantics seem questionable  (Peter Geoghegan <pg@heroku.com>)
Список pgsql-hackers
Дерево обсуждения
On Mon, May 18, 2015 at 9:03 PM Andrew Dunstan <andrew@dunslane.net> wrote:
So you're arguing that we shouldn't call the operation in question ||
because it's pretty much the same, mutatis mutandis, as the hstore
operation of the same name. You've lost me.

Hopefully this helps. Peter's argument, as I understand it is:

In hstore @> means unnested containment, in jsonb it means nested containment. Therefore, when an hstore operator is applied to jsonb it gets "nestedness" as jsonb is nested and adds that nestedness is an important thing that sets it apart from hstore. Therefore, since || is unnested concatenation in hstore, it should become nested concatenation for jsonb.

I don't know if the argument is strong enough but it does make some sense.

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Peter Geoghegan
Дата:
Сообщение: Re: jsonb concatenate operator's semantics seem questionable
Следующее
От: Peter Geoghegan
Дата:
Сообщение: Re: jsonb concatenate operator's semantics seem questionable