Re: jsonb concatenate operator's semantics seem questionable - Mailing list pgsql-hackers

From Jim Nasby
Subject Re: jsonb concatenate operator's semantics seem questionable
Date
Msg-id 555F77B7.3070604@BlueTreble.com
Whole thread Raw
In response to Re: jsonb concatenate operator's semantics seem questionable  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: jsonb concatenate operator's semantics seem questionable
List pgsql-hackers
On 5/21/15 4:25 PM, Andrew Dunstan wrote:
> Here is a patch that renames jsonb_replace to jsonb_set with a boolean
> create_missing flag that defaults to false (should we default it to
> true?). With the flag set it's more or less upsert for jsonb. Without,
> it's just update.

I think upsert is probably the more expected behavior.

Though, I'm also wondering if we should allow for throwing an error if 
path doesn't already exist (it looks like if create_missing is false it 
silently does nothing right now?)
-- 
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com



pgsql-hackers by date:

Previous
From: Fabrízio de Royes Mello
Date:
Subject: Re: Change pg_cancel_*() to ignore current backend
Next
From: Pavel Stehule
Date:
Subject: Re: Change pg_cancel_*() to ignore current backend