From a4a5c0cf9cec3df2d1662a799c539c2cc84aa463 Mon Sep 17 00:00:00 2001 From: Peter Eisentraut Date: Thu, 26 Sep 2019 16:35:10 +0200 Subject: [PATCH] doc: Update a confusing sentence about SQL/JSON Author: Liudmila Mantrova Reported-by: Jeff Janes Discussion: https://www.postgresql.org/message-id/flat/CAMkU%3D1wP-SO4KpiLxHJuPezTJCmK%3DJqefLXrr3eXFO7Qku%2BtMg%40mail.gmail.com --- doc/src/sgml/json.sgml | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/doc/src/sgml/json.sgml b/doc/src/sgml/json.sgml index 45b22b6e2d..6ff8751870 100644 --- a/doc/src/sgml/json.sgml +++ b/doc/src/sgml/json.sgml @@ -641,8 +641,7 @@ SELECT jdoc->'guid', jdoc->'name' FROM api WHERE jdoc @> '{"tags": ["qu - The SQL/JSON path language is fully integrated into the SQL engine: - the semantics of its predicates and operators generally follow SQL. + The semantics of SQL/JSON path predicates and operators generally follow SQL. At the same time, to provide a most natural way of working with JSON data, SQL/JSON path syntax uses some of the JavaScript conventions: