Re: Tackling JsonPath support - Mailing list pgsql-hackers

From Christian Convey
Subject Re: Tackling JsonPath support
Date
Msg-id CAPfS4Zx+X9YSYXM4q3+PAnSw79xSWukZG9XmLTKz2StXvtpj-Q@mail.gmail.com
Whole thread Raw
In response to Re: Tackling JsonPath support  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-hackers
On Mon, Nov 28, 2016 at 5:20 AM, Pavel Stehule <pavel.stehule@gmail.com> wrote:
...
Incremental work is great idea - I like this this style. Instead contrib, you can use public repository on github. Minimally for first stage is better to live outside core - you are not restricted by PostgreSQL development process. When your code will be stabilized, then you can go to commitfest. I believe so we need good JSON support. The XML support helps to PostgreSQL lot of, JSON will be great too.

​Hi Pavel,

Thanks for the suggestion.

I am planning to use one of my own public github repos as the location for my work.

I thought by adding my first implementation to "contrib", we could make this functionality available to end-users, even before there was a consensus about what PG's "official" JSON-related operators should have for syntax and semantics.

Does my reasoning make sense?

- C
 

pgsql-hackers by date:

Previous
From: Andrew Borodin
Date:
Subject: GIN non-intrusive vacuum of posting tree
Next
From: Corey Huinker
Date:
Subject: PSQL commands: \quit_if, \quit_unless