From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Nico Williams <nico(at)cryptonector(dot)com> |
Cc: | Christian Convey <christian(dot)convey(at)gmail(dot)com>, Petr Jelinek <petr(at)2ndquadrant(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, David Fetter <david(at)fetter(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Subject: | Re: Tackling JsonPath support |
Date: | 2016-12-05 16:53:06 |
Message-ID: | CA+Tgmob301hmgJsWXVFNDgDQg7=F+dnXcpAzYJJCn0widqdD4g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Dec 5, 2016 at 11:42 AM, Nico Williams <nico(at)cryptonector(dot)com> wrote:
>> Library integrations are tricky but, since you wrote JQ and seem
>
> Just to be clear, Stephen Dolan wrote jq. I've added to, and maintained
> jq, to be sure, but I would not want to take credit from Stephen.
Ah, OK, sorry for misunderstanding.
>> potentially willing to modify it to work with PostgreSQL better, this
>> one might be a lot less painful than some. I can't promise we'd
>> accept an integration even if you came up with a patch, but I see
>> looking back over this thread that there are several people cautiously
>> supporting the idea of using JQ in some form, which is promising.
>
> Fair enough. I won't be able to work on an integration for a few more
> months, so we'll see (and Stephen might well veto some such changes to
> jq), and it is time for me to shut up about this for now. Thanks for
> the very useful comments, and sorry for the noise.
Not noise at all. Thanks for your interest. Bandwidth is a little
limited around here so it's hard to give everyone the feedback that
they deserve, but it's good that you're interested.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2016-12-05 16:58:40 | Re: pg_dump / copy bugs with "big lines" ? |
Previous Message | Tom Lane | 2016-12-05 16:52:57 | Re: Tackling JsonPath support |