| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: JSONB in-place updates? |
| Date: | 2014-04-15 02:23:12 |
| Message-ID: | CAB7nPqRoPuGTM-bM5YY+p=bA94vPF802i=Bz2khvmXQEYCvUuQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Apr 15, 2014 at 5:16 AM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
> On 04/14/2014 09:27 AM, kelas wrote:
>> Are there any plans to add "in-place at-depth" update operator for JSONB
>> type, e.g.:
>>
>> UPDATE test SET attrs->'anwser' = 42 where attrs->'answer' = 41
>>
>
> Plans, yes. But not until 9.5, or maybe as an extension.
A custom function of the type find_and_modify(jsonb_data, key_name,
new_value) combined with the uniqueness of jsonb keys would be a good
workaround for now.
Regards,
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2014-04-15 02:23:24 | Re: API change advice: Passing plan invalidation info from the rewriter into the planner? |
| Previous Message | Andrew Dunstan | 2014-04-15 02:21:47 | Re: assertion failure 9.3.4 |