Re: Json(b) extension - Mailing list pgsql-hackers

From Dmitry Dolgov
Subject Re: Json(b) extension
Date
Msg-id CA+q6zcXN-JcAXTpkVPOW4t70ippnBANrkD8PUzV6u7+hEPg5Gw@mail.gmail.com
Whole thread Raw
In response to Re: Json(b) extension  (Josh Berkus <josh@agliodbs.com>)
List pgsql-hackers
>>> If your goal is to make this functionality available as soon as possible to users, an external extension is the way to go.
No, my primary goal is to create the useful contrib extension and help to the community =)
So, I also want to do it as a pgxn extension.


On 25 April 2014 00:11, Josh Berkus <josh@agliodbs.com> wrote:
On 04/24/2014 03:46 AM, Dmitry Dolgov wrote:
> Hi all,
>
> As you know, PostgreSQL introduced Json(b) support at the 9.4 version [1],
> and hstore v2.0 saved in separate repository [2]. But although PostgreSQL
> has this support at the core level, there are many useful functions, which
> wasn't ported to Json(b) from hstore v2.0 and json. Here [3], I've made a
> review of the missing Json(b) functions, which can be implemented. This
> list can be updated in the future, of course. I want to implement the
> missing functions in the form of extension (e.g. contrib/jsonx).

Thanks for making this list!

>
> What do you think about this?

I think you should do it as a pgxn extension, for now.  For it to be in
contrib/ or core, we'd need to argue extensively about the names of
operators and functions, which will take a while.    If your goal is to
make this functionality available as soon as possible to users, an
external extension is the way to go.

--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com


--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Composite Datums containing toasted fields are a bad idea(?)
Next
From: Hadi Moshayedi
Date:
Subject: Re: A question about code in DefineRelation()