From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Oleg Bartunov <obartunov@postgrespro.ru>
Cc: pgsql-docs@lists.postgresql.org
Subject: Re: SQL-2016 in docs
Date: Mon, 3 Jun 2019 21:39:34 +0200
Message-ID: <b441cb7f-21b0-e9fd-cfd6-ce63624a81fc@2ndquadrant.com> (raw)
In-Reply-To: <CAF4Au4yYbiZ+JjkPpOWjj=gPVjq2Q+PGJpyjVhL4W3RWB7B6BA@mail.gmail.com>
References: <CAF4Au4zH8HsV0Or7KiD2j7UstgDoXOnG+tZpwfY_wwpLuWP3Zg@mail.gmail.com>
<fce5fc4f-6442-6461-9177-a5286c3e5cc1@2ndquadrant.com>
<CAF4Au4yYbiZ+JjkPpOWjj=gPVjq2Q+PGJpyjVhL4W3RWB7B6BA@mail.gmail.com>
On 2019-05-30 16:34, Oleg Bartunov wrote:
> On Mon, May 27, 2019 at 2:33 PM Peter Eisentraut
> <peter.eisentraut@2ndquadrant.com> wrote:
>>
>> On 2019-05-12 10:14, Oleg Bartunov wrote:
>>> I noticed that in our docs for PG12 there is no SQL-2016, but we actually
>>> have JSON Path implementation committed, which is a part of SQL-2016
>>> standard. One missing feature - is datetime support. Peter, will you
>>> add this or I prepare the patch ?
>>
>> I did a rough check of the SQL:2016 JSON path specification versus our
>> regression tests, and came up with the attached supported feature list.
>> Would you like to confirm it?
>
> I confirm it.
pushed
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: peter.eisentraut@2ndquadrant.com, obartunov@postgrespro.ru, pgsql-docs@lists.postgresql.org
Subject: Re: SQL-2016 in docs
In-Reply-To: <b441cb7f-21b0-e9fd-cfd6-ce63624a81fc@2ndquadrant.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox