Re: SQL-2016 in docs

2019-06-03 Thread Peter Eisentraut
On 2019-05-30 16:34, Oleg Bartunov wrote: > On Mon, May 27, 2019 at 2:33 PM Peter Eisentraut > 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-20

Re: SQL-2016 in docs

2019-05-30 Thread Oleg Bartunov
On Mon, May 27, 2019 at 2:33 PM Peter Eisentraut 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 dateti

Re: SQL-2016 in docs

2019-05-27 Thread 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

Re: SQL-2016 in docs

2019-05-14 Thread 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

SQL-2016 in docs

2019-05-12 Thread 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.postgres