pg.ddx.io pgsql-docs@postgresql.org mailing list archive
help / color / mirror / Atom feedSQL-2016 in docs
5+ messages / 2 participants
[nested] [flat]
* SQL-2016 in docs
@ 2019-05-12 08:14 Oleg Bartunov <obartunov@postgrespro.ru>
0 siblings, 2 replies; 5+ messages in thread
From: Oleg Bartunov @ 2019-05-12 08:14 UTC (permalink / raw)
To: pgsql-docs@lists.postgresql.org, Peter Eisentraut <peter@eisentraut.org>
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
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: SQL-2016 in docs
@ 2019-05-14 13:57 Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
parent: Oleg Bartunov <obartunov@postgrespro.ru>
1 sibling, 0 replies; 5+ messages in thread
From: Peter Eisentraut @ 2019-05-14 13:57 UTC (permalink / raw)
To: Oleg Bartunov <obartunov@postgrespro.ru>; pgsql-docs@lists.postgresql.org
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
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: SQL-2016 in docs
@ 2019-05-27 11:33 Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
parent: Oleg Bartunov <obartunov@postgrespro.ru>
1 sibling, 1 reply; 5+ messages in thread
From: Peter Eisentraut @ 2019-05-27 11:33 UTC (permalink / raw)
To: Oleg Bartunov <obartunov@postgrespro.ru>; pgsql-docs@lists.postgresql.org
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.patch (text/plain, 1.7K) download
From fba85c745f4e84da369c623b518fcbf0718998f0 Mon Sep 17 00:00:00 2001
From: Peter Eisentraut <peter@eisentraut.org>
Date: Mon, 27 May 2019 12:05:18 +0200
Subject: [PATCH] Update SQL conformance information about JSON path
---
src/backend/catalog/sql_features.txt | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/src/backend/catalog/sql_features.txt b/src/backend/catalog/sql_features.txt
index 68da18b3bc..ae874f38ee 100644
--- a/src/backend/catalog/sql_features.txt
+++ b/src/backend/catalog/sql_features.txt
@@ -543,13 +543,13 @@ T827 JSON_TABLE: sibling NESTED COLUMNS clauses NO
T828 JSON_QUERY NO
T829 JSON_QUERY: array wrapper options NO
T830 Enforcing unique keys in SQL/JSON constructor functions NO
-T831 SQL/JSON path language: strict mode NO
-T832 SQL/JSON path language: item method NO
-T833 SQL/JSON path language: multiple subscripts NO
-T834 SQL/JSON path language: wildcard member accessor NO
-T835 SQL/JSON path language: filter expressions NO
-T836 SQL/JSON path language: starts with predicate NO
-T837 SQL/JSON path language: regex_like predicate NO
+T831 SQL/JSON path language: strict mode YES
+T832 SQL/JSON path language: item method NO datetime() not yet implemented
+T833 SQL/JSON path language: multiple subscripts YES
+T834 SQL/JSON path language: wildcard member accessor YES
+T835 SQL/JSON path language: filter expressions YES
+T836 SQL/JSON path language: starts with predicate YES
+T837 SQL/JSON path language: regex_like predicate YES
T838 JSON_TABLE: PLAN DEFAULT clause NO
T839 Formatted cast of datetimes to/from character strings NO
M001 Datalinks NO
--
2.21.0
* Re: SQL-2016 in docs
@ 2019-05-30 14:34 Oleg Bartunov <obartunov@postgrespro.ru>
parent: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
0 siblings, 1 reply; 5+ messages in thread
From: Oleg Bartunov @ 2019-05-30 14:34 UTC (permalink / raw)
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>; +Cc: pgsql-docs@lists.postgresql.org
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
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: SQL-2016 in docs
@ 2019-06-03 19:39 Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
parent: Oleg Bartunov <obartunov@postgrespro.ru>
0 siblings, 0 replies; 5+ messages in thread
From: Peter Eisentraut @ 2019-06-03 19:39 UTC (permalink / raw)
To: Oleg Bartunov <obartunov@postgrespro.ru>; +Cc: pgsql-docs@lists.postgresql.org
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
^ permalink raw reply [nested|flat] 5+ messages in thread
end of thread, other threads:[~2019-06-03 19:39 UTC | newest]
Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2019-05-12 08:14 SQL-2016 in docs Oleg Bartunov <obartunov@postgrespro.ru>
2019-05-14 13:57 ` Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
2019-05-27 11:33 ` Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
2019-05-30 14:34 ` Oleg Bartunov <obartunov@postgrespro.ru>
2019-06-03 19:39 ` Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
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