| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Dmitry Dolgov <9erthalion6(at)gmail(dot)com>, Thom Brown <thom(at)linux(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: jsonb_set array append hack? |
| Date: | 2015-09-21 21:21:57 |
| Message-ID: | 560074F5.6060705@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 09/21/2015 12:13 PM, Dmitry Dolgov wrote:
> > 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);
> ERROR: path element at the position 2 is not an integer
That seems reasonable. For that matter, we should probably disallow NULL
path elements also, shouldn't we?
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2015-09-21 21:53:40 | Re: Streaming Replication clusters and load balancing |
| Previous Message | Dmitry Vasilyev | 2015-09-21 20:59:50 | Re: Streaming Replication clusters and load balancing |