From 1f33f211bc531d257f84fefb9208dd43e8718972 Mon Sep 17 00:00:00 2001 From: Alexander Korotkov Date: Wed, 7 Aug 2019 16:06:45 +0300 Subject: [PATCH] Fix some typos in jsonpath documentation Discussion: https://postgr.es/m/8B7FA3B4-328D-43D7-95A8-37B8891B8C78%40winand.at Author: Markus Winand Backpatch-through: 12 --- doc/src/sgml/func.sgml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml index 7412df0bae..f1d1005ae2 100644 --- a/doc/src/sgml/func.sgml +++ b/doc/src/sgml/func.sgml @@ -11735,7 +11735,7 @@ table2-mapping A path expression can be a Boolean predicate, although the SQL/JSON standard allows predicates only in filters. This is necessary for implementation of the @@ operator. For example, - the followingjsonpath expression is valid in + the following jsonpath expression is valid in PostgreSQL: '$.track.segments[*].HR < 70' @@ -12997,7 +12997,7 @@ table2-mapping - select * jsonb_path_query('{"a":[1,2,3,4,5]}', '$.a[*] ? (@ >= $min && @ <= $max)', '{"min":2,"max":4}'); + select * from jsonb_path_query('{"a":[1,2,3,4,5]}', '$.a[*] ? (@ >= $min && @ <= $max)', '{"min":2,"max":4}');