Re: jsonb_set array append hack?
От | Dmitry Dolgov |
---|---|
Тема | Re: jsonb_set array append hack? |
Дата | |
Msg-id | CA+q6zcV=z_daXD8U-Kgt9hU9Xo=4Le3pKmKT6T6O9OBBvj_CVw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: jsonb_set array append hack? (Thom Brown <thom@linux.com>) |
Ответы |
Re: jsonb_set array append hack?
|
Список | pgsql-hackers |
> I would expect some kind of error. We're trying to address a position in an array, and we're instead passing a key. If it completes successfully, the chances are it isn't what the user intended.
Thanks for the explanation. So, basically, it should be like this, am I right?
postgres=# SELECT jsonb_set(
'{"name": "Joe", "vehicle_types": ["car", "van"]}'::jsonb,
'{vehicle_types, nonsense}',
'"motorcycle"', true);
'{vehicle_types, nonsense}',
'"motorcycle"', true);
ERROR: path element at the position 2 is not an integer
On 20 September 2015 at 23:50, Thom Brown <thom@linux.com> wrote:
On 20 September 2015 at 16:17, Dmitry Dolgov <9erthalion6@gmail.com> wrote:I'm sorry, but I'm not sure, what behavior is expected in this case?Right now the following logic was implemented:"we trying to set an element inside an array, but we've got a non-integer path item("nonsense" in this particular case), so we're going to add a new element at the end of array by default"If it's wrong, should we refuse to perform such kind of operations, or should we replace"vehicle_type": ["car", "van"]to"vehicle_type: {"nonsense": "motorcycle"}?(please bottom-post)I would expect some kind of error. We're trying to address a position in an array, and we're instead passing a key. If it completes successfully, the chances are it isn't what the user intended.Thom
Вложения
В списке pgsql-hackers по дате отправления: