Re: jsonb array-style subscripting

From: Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>
To: Josh Berkus <josh(at)agliodbs(dot)com>, Dmitry Dolgov <9erthalion6(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: jsonb array-style subscripting
Date: 2015-08-20 19:24:45
Message-ID: 55D6297D.3090903@BlueTreble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 8/17/15 4:25 PM, Josh Berkus wrote:
> On 08/17/2015 02:18 PM, Jim Nasby wrote:
>> >On 8/17/15 3:33 PM, Josh Berkus wrote:
>>> >>Again, how do we handle missing keys? Just return NULL? or ERROR? I'd
>>> >>prefer the former, but there will be arguments the other way.
>> >
>> >I've been wondering if we should add some kind of "strict" JSON. My big
>> >concern is throwing an error if you try to provide duplicate keys, but
>> >it seems reasonable that json_strict would throw an error if you try to
>> >reference something that doesn't exist.
> Only if there's demand for it. Is there?

I'm certainly worried (paranoid?) about it. Postgres is very good about
not silently dropping data and this seems a glaring departure from that.
I haven't looked yet but I'm hoping this could at least be added as an
extension without duplicating a bunch of the existing JSON stuff.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Data in Trouble? Get it in Treble! http://BlueTreble.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Feng Tian 2015-08-20 19:42:46 Re: Using quicksort for every external sort run
Previous Message Jim Nasby 2015-08-20 19:16:22 Re: proposal: function parse_ident