Re: jsonb array-style subscripting

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>
Cc: Dmitry Dolgov <9erthalion6(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: jsonb array-style subscripting
Date: 2015-08-18 05:32:42
Message-ID: CAFj8pRBXNT=OSSZB2WYkDQO8QfJC3e-9B4Xtj+i5CtvB1bETpw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi

2015-08-17 21:12 GMT+02:00 Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)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(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Noah Misch 2015-08-18 05:57:43 Re: Test code is worth the space
Previous Message Michael Paquier 2015-08-18 05:21:22 Re: missing documentation for partial WAL files