From: | Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru> |
---|---|
To: | Thom Brown <thom(at)linux(dot)com>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: SQL/JSON path issues/questions |
Date: | 2019-06-14 20:44:49 |
Message-ID: | CAPpHfdvHv_tx5gduN16yYFOK8LS1_THcJeAJ=W7bYcUsAw+NJA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Jun 13, 2019 at 5:00 PM Thom Brown <thom(at)linux(dot)com> wrote:
> I've been reading through the documentation regarding jsonpath and
> jsonb_path_query etc., and I have found it lacking explanation for
> some functionality, and I've also had some confusion when using the
> feature.
BTW, I've some general idea about jsonpath documentation structure.
Right now definition of jsonpath language is spread between sections
"JSON Types" [1] and "JSON Functions, Operators, and Expressions" [2].
Thank might be confusing. I think it would be more readable if whole
jsonpath language definition would be given in a single place. I
propose to move whole definition of jsonpath to section [1] leaving
section [2] just with SQL-level functions. Any thoughts?
Links.
1. https://www.postgresql.org/docs/devel/datatype-json.html#DATATYPE-JSONPATH
2. https://www.postgresql.org/docs/devel/functions-json.html#FUNCTIONS-SQLJSON-PATH
------
Alexander Korotkov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2019-06-14 20:48:35 | Re: CREATE STATISTICS documentation bug |
Previous Message | Christopher Browne | 2019-06-14 20:29:34 | Re: UCT (Re: pgsql: Update time zone data files to tzdata release 2019a.) |