summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPeter Eisentraut <peter@eisentraut.org>2019-09-26 16:35:10 +0200
committerPeter Eisentraut <peter@eisentraut.org>2019-09-26 16:35:10 +0200
commitbaca53d3dca701e6a8b04a1b2dd0ed603289fbf0 (patch)
treece31acf971b49fe285d9d9e7a88427bd0c6f6858
parentb4d615aaa1ecedcf1e2ca415cd2893d1f18aeeca (diff)
doc: Update a confusing sentence about SQL/JSON
Author: Liudmila Mantrova <l.mantrova@postgrespro.ru> Reported-by: Jeff Janes <jeff.janes@gmail.com> Discussion: https://www.postgresql.org/message-id/flat/CAMkU%3D1wP-SO4KpiLxHJuPezTJCmK%3DJqefLXrr3eXFO7Qku%2BtMg%40mail.gmail.com
-rw-r--r--doc/src/sgml/json.sgml3
1 files changed, 1 insertions, 2 deletions
diff --git a/doc/src/sgml/json.sgml b/doc/src/sgml/json.sgml
index 45b22b6e2d2..6ff87518705 100644
--- a/doc/src/sgml/json.sgml
+++ b/doc/src/sgml/json.sgml
@@ -641,8 +641,7 @@ SELECT jdoc-&gt;'guid', jdoc-&gt;'name' FROM api WHERE jdoc @&gt; '{"tags": ["qu
</para>
<para>
- 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:
</para>