| From: | Oleg Bartunov <obartunov(at)gmail(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, Nikita Glukhov <n(dot)gluhov(at)postgrespro(dot)ru>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>, Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Subject: | Re: SQL/JSON: functions |
| Date: | 2018-03-14 00:08:17 |
| Message-ID: | CAF4Au4zRD-5K89Z_coU2VJe98JBN2JpKi7h7djVPiu_Q1FzA1Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 14 Mar 2018 01:54, "Michael Paquier" <michael(at)paquier(dot)xyz> wrote:
On Tue, Mar 13, 2018 at 04:08:01PM +0300, Oleg Bartunov wrote:
> The docs are here
> https://github.com/obartunov/sqljsondoc/blob/master/README.jsonpath.md
>
> It's not easy to write docs for SQL/JSON in xml, so I decided to write in
more
> friendly way. We'll have time to convert it to postgres format.
If you aim at getting a feature committed first without its
documentation, and getting the docs written after the feature freeze
using a dedicated open item or such,
Exactly. SQL/JSON is rather complex thing and "converting" the standard to
the user level understanding is a separate challenge and I'd like to
continue to work on it. It's mostly written, we need to understand how to
organize it.
this
is much acceptable in my
opinion and the CF is running short in time.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tatsuo Ishii | 2018-03-14 00:08:59 | Re: Fixes for missing schema qualifications |
| Previous Message | Thomas Munro | 2018-03-13 23:57:57 | Re: neqjoinsel versus "refresh materialized view concurrently" |