From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
---|---|
To: | Thom Brown <thom(at)linux(dot)com>, Dmitry Dolgov <9erthalion6(at)gmail(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: GSoC 2015: Extra Jsonb functionality |
Date: | 2015-03-20 23:51:51 |
Message-ID: | 550CB297.3070102@BlueTreble.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2015-03-21 00:50:03 | Re: proposal: doc: simplify examples of dynamic SQL |
Previous Message | Jim Nasby | 2015-03-20 23:44:03 | Re: Superuser connect during smart shutdown |