pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Oleg Bartunov <obartunov@postgrespro.ru>
To: pgsql-docs@lists.postgresql.org
Subject: Re: SQL-2016 in docs
Date: Mon, 27 May 2019 13:33:36 +0200
Message-ID: <fce5fc4f-6442-6461-9177-a5286c3e5cc1@2ndquadrant.com> (raw)
In-Reply-To: <CAF4Au4zH8HsV0Or7KiD2j7UstgDoXOnG+tZpwfY_wwpLuWP3Zg@mail.gmail.com>
References: <CAF4Au4zH8HsV0Or7KiD2j7UstgDoXOnG+tZpwfY_wwpLuWP3Zg@mail.gmail.com>

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

view thread (5+ messages)  latest in thread

Message-ID: <fce5fc4f-6442-6461-9177-a5286c3e5cc1@2ndquadrant.com>
Permalink:  ../fce5fc4f-6442-6461-9177-a5286c3e5cc1@2ndquadrant.com/
Also on:    postgresql.org/message-id/fce5fc4f-6442-6461-9177-a5286c3e5cc1@2ndquadrant.com

 ·  · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-docs@postgresql.org
  Cc: peter.eisentraut@2ndquadrant.com, obartunov@postgrespro.ru, pgsql-docs@lists.postgresql.org
  Subject: Re: SQL-2016 in docs
  In-Reply-To: <fce5fc4f-6442-6461-9177-a5286c3e5cc1@2ndquadrant.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

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