Re: jsonb array-style subscripting
Pavel Stehule <pavel.stehule@gmail.com>
From: Pavel Stehule <pavel.stehule@gmail.com>
To: Jim Nasby <Jim.Nasby@bluetreble.com>
Cc: Dmitry Dolgov <9erthalion6@gmail.com>,
PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2015-08-18T05:32:42Z
Lists: pgsql-hackers
Hi
2015-08-17 21:12 GMT+02:00 Jim Nasby <Jim.Nasby@bluetreble.com>:
> On 8/17/15 12:57 PM, Dmitry Dolgov wrote:
>
>> * is it interesting for the community?
>>
>
> We definitely need better ways to manipulate JSON.
>
> * is that a good idea to extend the `ArrayRef` for jsonb? If it's
>> appropriate, probably we can rename it to `ArrayJsonbRef` of something.
>> * what can be improved in the code at the top level (function placement,
>> probably, functionality duplication, etc.)?
>> * are there any special cases, that I should take care of in this
>> implementation?
>>
>
> How would this work when you have a JSON array? Postgres array syntax
> suddenly becoming key/value syntax for JSON seems like a pretty bad idea to
> me. Could a different syntax (maybe {}) be used instead?
>
I don't understand why '{}' should be better than '[]' ?
The lot of modern languages doesn't different between arrays and hash.
Regards
Pavel
>
> I'm not sure having the UPDATE you show cause objects to spring to life is
> so great either.
> --
> Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
> Data in Trouble? Get it in Treble! http://BlueTreble.com
>
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>
Commits
-
Throw error when assigning jsonb scalar instead of a composite object
- aa6e46daf530 14.0 landed
-
Filling array gaps during jsonb subscripting
- 81fcc72e6622 14.0 landed
-
Implementation of subscripting for jsonb
- 676887a3b0b8 14.0 landed