Re: fixes for typos and tags in REL_12_STABLE

2019-09-13 Thread Alexander Korotkov
On Thu, Sep 12, 2019 at 5:38 PM Alvaro Herrera  wrote:
>
> On 2019-Sep-12, Alexander Korotkov wrote:
>
> > On Thu, Sep 12, 2019 at 4:58 PM Liudmila Mantrova  
> > wrote:
> > > Please consider these small patches for REL_12_STABLE that mainly fix 
> > > remaining typos and some tagging issues. The jsonpath-related one also 
> > > improves some wordings, e.g. there seems to be no need to separate 
> > > Boolean operators with spaces in path definitions.
> >
> > I'm going to push these two if no objections.
>
> Looks good on a quick once-over.

Pushed, thanks!

--
Alexander Korotkov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company




Re: fixes for typos and tags in REL_12_STABLE

2019-09-12 Thread Alvaro Herrera
On 2019-Sep-12, Alexander Korotkov wrote:

> On Thu, Sep 12, 2019 at 4:58 PM Liudmila Mantrova  
> wrote:
> > Please consider these small patches for REL_12_STABLE that mainly fix 
> > remaining typos and some tagging issues. The jsonpath-related one also 
> > improves some wordings, e.g. there seems to be no need to separate Boolean 
> > operators with spaces in path definitions.
> 
> I'm going to push these two if no objections.

Looks good on a quick once-over.

-- 
Álvaro Herrerahttps://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services




fixes for typos and tags in REL_12_STABLE

2019-09-12 Thread Liudmila Mantrova
Hi,

Please consider these small patches for REL_12_STABLE that mainly fix
remaining typos and some tagging issues. The jsonpath-related one also
improves some wordings, e.g. there seems to be no need to separate Boolean
operators with spaces in path definitions.

-- 
Best regards,
Liudmila Mantrova

Technical writer at Postgres Professional: http://www.postgrespro.com
diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml
index 0d6d883dbf..829ad07a90 100644
--- a/doc/src/sgml/func.sgml
+++ b/doc/src/sgml/func.sgml
@@ -11544,7 +11544,7 @@ table2-mapping
 
   JSON query functions and operators
pass the provided path expression to the path engine
-   for evaluation. If the expression matches the JSON data to be queried,
+   for evaluation. If the expression matches the queried JSON data,
the corresponding SQL/JSON item is returned.
Path expressions are written in the SQL/JSON path language
and can also include arithmetic expressions and functions.
@@ -11604,7 +11604,7 @@ table2-mapping
 
   
If the item to retrieve is an element of an array, you have
-   to unnest this array using the [*] operator. For example,
+   to unnest this array using the [*] operator. For example,
the following path will return location coordinates for all
the available track segments:
 
@@ -11625,8 +11625,7 @@ table2-mapping
The result of each path evaluation step can be processed
by one or more jsonpath operators and methods
listed in .
-   Each method must be preceded by a dot, while arithmetic and Boolean
-   operators are separated from the operands by spaces. For example,
+   Each method name must be preceded by a dot. For example,
you can get an array size:
 
 '$.track.segments.size()'
@@ -11907,7 +11906,7 @@ table2-mapping


 double()
-Approximate numeric value converted from a string
+Approximate floating-point number converted from an SQL/JSON number or a string
 {"len": "1.9"}
 $.len.double() * 2
 3.8
@@ -11936,10 +11935,10 @@ table2-mapping

 keyvalue()
 
-  Sequence of object's key-value pairs represented as array of objects
+  Sequence of object's key-value pairs represented as array of items
   containing three fields ("key",
   "value", and "id").
-  "id" is an unique identifier of the object
+  "id" is a unique identifier of the object
   key-value pair belongs to.
 
 {"x": "20", "y": 32}
@@ -12061,9 +12060,9 @@ table2-mapping
 like_regex
 
   Tests pattern matching with POSIX regular expressions
-  ().  Supported flags
+  (see ).  Supported flags
   are i, s, m,
-  x and q.
+  x, and q.
 ["abc", "abd", "aBdC", "abdacb", "babc"]
 $[*] ? (@ like_regex "^ab.*c" flag "i")
 "abc", "aBdC", "abdacb"
@@ -12077,7 +12076,7 @@ table2-mapping


 exists
-Tests whether a path expression has at least one SQL/JSON item
+Tests whether a path expression matches at least one SQL/JSON item
 {"x": [1, 2], "y": [2, 4]}
 strict $.* ? (exists (@ ? (@[*] > 2)))
 2, 4
@@ -12302,10 +12301,9 @@ table2-mapping

 @@
 jsonpath
-JSON path predicate check result for the specified JSON value.
-Only first result item is taken into account.  If there are no results
-or the first result item is not Boolean, then null
-is returned.
+Returns the result of JSON path predicate check for the specified JSON value.
+Only the first item of the result is taken into account.  If the
+result is not Boolean, then null is returned.
 '{"a":[1,2,3,4,5]}'::jsonb @@ '$.a[*] > 2'

   
@@ -12943,7 +12941,7 @@ table2-mapping

 
  
-   jsonb_path_exists(target jsonb, path jsonpath [, vars jsonb, silent bool])
+   jsonb_path_exists(target jsonb, path jsonpath [, vars jsonb [, silent bool]])
  
 
 boolean
@@ -12968,10 +12966,9 @@ table2-mapping
 
 boolean
 
-  Returns JSON path predicate result for the specified JSON value.
-  Only first result item is taken into account.  If there are no results
-  or the first result item is not Boolean, then null
-  is returned.
+  Returns the result of JSON path predicate check for the specified JSON value.
+  Only the first item of the result is taken into account.  If the
+  result is not Boolean, then null is returned.
 
 
  
@@ -13178,18 +13175,18 @@ table2-mapping
   

 The jsonb_path_exists, jsonb_path_match,
-jsonb_path_query, jsonb_path_query_array and
+jsonb_path_query, jsonb_path_query_array, and
 jsonb_path_query_first
 functions have optional vars and silent
 arguments.



Re: fixes for typos and tags in REL_12_STABLE

2019-09-12 Thread Alexander Korotkov
On Thu, Sep 12, 2019 at 4:58 PM Liudmila Mantrova  wrote:
> Please consider these small patches for REL_12_STABLE that mainly fix 
> remaining typos and some tagging issues. The jsonpath-related one also 
> improves some wordings, e.g. there seems to be no need to separate Boolean 
> operators with spaces in path definitions.

I'm going to push these two if no objections.

--
Alexander Korotkov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company