| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Oleg Bartunov <obartunov(at)postgrespro(dot)ru> |
| Cc: | pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: SQL-2016 in docs |
| Date: | 2019-06-03 19:39:34 |
| Message-ID: | b441cb7f-21b0-e9fd-cfd6-ce63624a81fc@2ndquadrant.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On 2019-05-30 16:34, Oleg Bartunov wrote:
> On Mon, May 27, 2019 at 2:33 PM Peter Eisentraut
> <peter(dot)eisentraut(at)2ndquadrant(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2019-06-03 21:20:42 | Re: initdb recommendations |
| Previous Message | Noah Misch | 2019-06-03 00:55:39 | Re: initdb recommendations |