Обсуждение: SQL-2016 in docs

Поиск
Список
Период
Сортировка

SQL-2016 in docs

От
Oleg Bartunov
Дата:
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 ?

Oleg
-- 
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company



Re: SQL-2016 in docs

От
Peter Eisentraut
Дата:
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 have now updated the feature list to SQL:2016.  All the
SQL/JSON-related features are currently set to "NO".  Please propose
patches to update that.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



Re: SQL-2016 in docs

От
Peter Eisentraut
Дата:
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?

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Вложения

Re: SQL-2016 in docs

От
Oleg Bartunov
Дата:
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.

>
> --
> Peter Eisentraut              http://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



-- 
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company



Re: SQL-2016 in docs

От
Peter Eisentraut
Дата:
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