Subject: Re: Tackling JsonPath support
To: Christian Convey <christian.convey@gmail.com>,
 Pavel Stehule <pavel.stehule@gmail.com>,
 "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>,
 Tom Lane <tgl@sss.pgh.pa.us>
References: 
 <CAPfS4Zy0RCJstWT3sRhKZO6db+xxZeAL7wmOVG5QUK=P8bXWZQ@mail.gmail.com>
 <CAFj8pRA2BbWioAfA79bDdJ_JviVaUYr+5zj+sQuVrHmvJARKdw@mail.gmail.com>
 <CAPfS4ZwaPMMLUQ6AFj=t182AAce-wGcDWzP9nHqkz3nx+H2_2Q@mail.gmail.com>
 <20681.1479057226@sss.pgh.pa.us>
 <CAFj8pRDvKiQ3YcNOCeEcOEy+OKh6LFcazmOe-Tit-gHyv1e+xQ@mail.gmail.com>
 <CAPfS4Zx8v1xx_OoG6n2_K2TthNudGshfkSbk=-__N+1-z8WSwg@mail.gmail.com>
 <CAFj8pRAYcPFfiX=R=GnFop9Czbu1ArR3CczH-v0JZG8v-xUG_Q@mail.gmail.com>
 <CAPfS4Zx+X9YSYXM4q3+PAnSw79xSWukZG9XmLTKz2StXvtpj-Q@mail.gmail.com>
 <CAFj8pRDNmWSQyzGGOyy9yWdL3fikik5n=xNOzv7QxOD0wW5nPw@mail.gmail.com>
 <CAFj8pRBgG-WC4eJC+grM4EtkrXZZUNMwmY2aCwcwfV5sbAd0tQ@mail.gmail.com>
 <CAPfS4ZyeGBZa4fCKu=d4hTa3CTjFgYRE_zEeS+F3B2Xao3EWNw@mail.gmail.com>
From: Petr Jelinek <petr@2ndquadrant.com>
Message-ID: <a097265c-a701-4099-6bd4-1e2c0a1340d3@2ndquadrant.com>
Date: Mon, 28 Nov 2016 22:41:51 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101
 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: 
 <CAPfS4ZyeGBZa4fCKu=d4hTa3CTjFgYRE_zEeS+F3B2Xao3EWNw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org


On 28/11/16 18:57, Christian Convey wrote:
> 
> On Mon, Nov 28, 2016 at 9:47 AM, Pavel Stehule <pavel.stehule@gmail.com
> <mailto:pavel.stehule@gmail.com>> wrote
> 
>     > 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.
>     >
> 
>     this time the commiters dislike the contrib dir. It is hard to push
>     there anything :-(. You can try it, but it can be lost time.
> 
> 
> ​Thanks for the warning.  I'm okay with  my patch adding the "json_path"
> function to the core PG code.​
> 
> I would still suggest that we hold off on having my first patch
> implement an official JSON-related operator such as "JSON_TABLE".  I
> would prefer to have my "json_path" function available to users even
> before we know how "JSON_TABLE", etc. should behave.
> 
> ​Does that sound reasonable?​
> 

Hi,

just make it extension, not contrib module, there is not much difference
between those except contrib is included in distribution.

Extensions that provide just functions are easy to integrate into core
(that's how some of the existing json functions were added in the past
as well).

-- 
  Petr Jelinek                  http://www.2ndQuadrant.com/
  PostgreSQL Development, 24x7 Support, Training & Services


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