Re: GSoC 2015: Extra Jsonb functionality

From: Dmitry Dolgov <9erthalion6(at)gmail(dot)com>
To: Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>
Cc: Thom Brown <thom(at)linux(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: GSoC 2015: Extra Jsonb functionality
Date: 2015-03-21 17:49:06
Message-ID: CA+q6zcXrXJ2+OhhRn8OfNWxW45GY9k1sKMCii5q=tYTt8_uG2g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> Frankly, I think the whole proposal needs to be rethought with an eye
towards supporting and preserving nested elements instead of trying to just
flatten everything out.

Can you pls show me few examples what do you mean exactly?

On 21 March 2015 at 06:51, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> wrote:

> On 3/19/15 9:07 AM, Thom Brown wrote:
>
>> > jsonb_to_array
>>> > ------------------------------
>>> > {a, 1, b, c, 2, d, 3, 4}
>>>
>> Is there a use-case for the example you've given above, where you take
>> JSON containing objects and arrays, and flatten them out into a
>> one-dimensional array?
>>
>
> There are a lot of things proposed here that are completely ignoring the
> idea of nested elements, which I think is a big mistake.
>
> Frankly, I think the whole proposal needs to be rethought with an eye
> towards supporting and preserving nested elements instead of trying to just
> flatten everything out. If a user wanted things flat they would have just
> started with that in the first place.
> --
> Jim Nasby, Data Architect, Blue Treble Consulting
> Data in Trouble? Get it in Treble! http://BlueTreble.com
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Thom Brown 2015-03-21 18:30:09 Re: assessing parallel-safety
Previous Message Jeff Janes 2015-03-21 17:25:10 Re: Remove fsync ON/OFF as a visible option?