Re: jsonb array-style subscripting
Jim Nasby <jim.nasby@bluetreble.com>
From: Jim Nasby <Jim.Nasby@BlueTreble.com>
To: Josh Berkus <josh@agliodbs.com>, Dmitry Dolgov <9erthalion6@gmail.com>,
PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2015-08-20T19:24:45Z
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
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