Re: [PATH] Jsonb, insert a new value into an array at arbitrary position

From: Dmitry Dolgov <9erthalion6(at)gmail(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Teodor Sigaev <teodor(at)sigaev(dot)ru>, Vitaly Burovoy <vitaly(dot)burovoy(at)gmail(dot)com>, David Steele <david(at)pgmasters(dot)net>, Petr Jelinek <petr(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATH] Jsonb, insert a new value into an array at arbitrary position
Date: 2016-04-06 04:13:59
Message-ID: CA+q6zcVxLhAF9eUrHhxsJQCkHjtaGOdg8wQcz93Z3B+rJeFNvA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 6 April 2016 at 03:29, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:

>
> Yeah, keeping it but rejecting update of an existing key is my preference
> too.
>
> cheers
>
> andrew
>

Yes, it sounds quite reasonable. Here is a new version of patch (it will
throw
an error for an existing key). Is it better now?

Attachment Content-Type Size
jsonb_insert_v7.patch text/x-patch 20.5 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Noah Misch 2016-04-06 04:42:35 Re: Updated backup APIs for non-exclusive backups
Previous Message Abhijit Menon-Sen 2016-04-06 02:56:28 Re: dealing with extension dependencies that aren't quite 'e'