SQL-2016 in docs
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
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
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
Attachments:
0001-Update-SQL-conformance-information-about-JSON-path.patchtext/plain; charset=UTF-8; name=0001-Update-SQL-conformance-information-about-JSON-path.patch; x-mac-creator=0; x-mac-type=0Download+7-8
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
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