Re: JSON Patch (RFC 6902) support?

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: JSON Patch (RFC 6902) support?
Date: 2014-03-13 17:24:44
Message-ID: 5321E9DC.7090204@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 03/13/2014 01:01 PM, Josh Berkus wrote:
> On 03/13/2014 09:53 AM, Ryan Pedela wrote:
>> This is my first email to the PostgreSQL mailing lists so I hope this is
>> the correct place. If not, please let me know.
>>
>> I was wondering if it would be possible and wise to support JSON Patch?
>> https://tools.ietf.org/html/rfc6902
>>
>> One of the problems I have as a user is how to update a portion of a JSON
>> object efficiently. Right now I have to read the entire field from the
>> database, update it, and then write it back. I am thinking JSON Patch might
>> be a good way to solve this problem because it would allow partial updates
>> and I think it could easily fit into the existing set of JSON functions
>> such as:
>>
>> // applies a JSON Patch
>> json_patch_apply(json, patch)
>>
>> // diffs two JSON objects and produces a JSON Patch
>> json_patch_diff(json a, json b)
> I can't speak to the technical difficulties, but *I* would use it.
>
> Note that on the backend Postgres is still going to re-write the entire
> JSON value. Also, we'd want both a json_patch and jsonb_patch, which
> would have the same syntax but different internal plumbing.
>

Some of this will be less than trivial especially for text-format json.

But without committing myself I'll be interested to see a patch.

cheers

andrew

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2014-03-13 17:55:07 Re: COPY table FROM STDIN doesn't show count tag
Previous Message Greg Stark 2014-03-13 17:23:29 Re: 9a57858f1103b89a5674f0d50c5fe1f756411df6