mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Doc: update sections 9.14 - 9.16 for new function table layout.

Browse Source 
Minor editorial changes in the first two sections; larger ones
in the JSON section.
This commit is contained in:
Tom Lane 2020-04-30 12:53:44 -04:00
parent eb892102e0
commit 30e82f1bc9
2 changed files with 2121 additions and 1537 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3629
doc/src/sgml/func.sgml
View File

File diff suppressed because it is too large Load Diff

29
doc/src/sgml/json.sgml
View File

@ -648,8 +648,8 @@ SELECT jdoc->'guid', jdoc->'name' FROM api WHERE jdoc @> '{"tags": ["qu
<para> <para>
The semantics of SQL/JSON path 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, At the same time, to provide a natural way of working with JSON data,
SQL/JSON path syntax uses some of the JavaScript conventions: SQL/JSON path syntax uses some JavaScript conventions:
</para> </para>
<itemizedlist> <itemizedlist>
@ -701,7 +701,7 @@ SELECT jdoc-&gt;'guid', jdoc-&gt;'name' FROM api WHERE jdoc @&gt; '{"tags": ["qu
<para> <para>
A path expression consists of a sequence of path elements, A path expression consists of a sequence of path elements,
which can be the following: which can be any of the following:
<itemizedlist> <itemizedlist>
<listitem> <listitem>
<para> <para>
@ -722,7 +722,7 @@ SELECT jdoc-&gt;'guid', jdoc-&gt;'name' FROM api WHERE jdoc @&gt; '{"tags": ["qu
<listitem> <listitem>
<para> <para>
<type>jsonpath</type> operators and methods listed <type>jsonpath</type> operators and methods listed
in <xref linkend="functions-sqljson-path-operators"/> in <xref linkend="functions-sqljson-path-operators"/>.
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
@ -751,7 +751,7 @@ SELECT jdoc-&gt;'guid', jdoc-&gt;'name' FROM api WHERE jdoc @&gt; '{"tags": ["qu
<tbody> <tbody>
<row> <row>
<entry><literal>$</literal></entry> <entry><literal>$</literal></entry>
<entry>A variable representing the JSON text to be queried <entry>A variable representing the JSON value being queried
(the <firstterm>context item</firstterm>). (the <firstterm>context item</firstterm>).
</entry> </entry>
</row> </row>
@ -759,9 +759,8 @@ SELECT jdoc-&gt;'guid', jdoc-&gt;'name' FROM api WHERE jdoc @&gt; '{"tags": ["qu
<entry><literal>$varname</literal></entry> <entry><literal>$varname</literal></entry>
<entry> <entry>
A named variable. Its value can be set by the parameter A named variable. Its value can be set by the parameter
<parameter>vars</parameter> of several JSON processing functions. <parameter>vars</parameter> of several JSON processing functions;
See <xref linkend="functions-json-processing-table"/> and see <xref linkend="functions-json-processing-table"/> for details.
its notes for details.
<!-- TODO: describe PASSING clause once implemented !--> <!-- TODO: describe PASSING clause once implemented !-->
</entry> </entry>
</row> </row>
@ -797,10 +796,10 @@ SELECT jdoc-&gt;'guid', jdoc-&gt;'name' FROM api WHERE jdoc @&gt; '{"tags": ["qu
<entry> <entry>
<para> <para>
Member accessor that returns an object member with Member accessor that returns an object member with
the specified key. If the key name is a named variable the specified key. If the key name matches some named variable
starting with <literal>$</literal> or does not meet the starting with <literal>$</literal> or does not meet the
JavaScript rules of an identifier, it must be enclosed in JavaScript rules for an identifier, it must be enclosed in
double quotes as a character string literal. double quotes to make it a string literal.
</para> </para>
</entry> </entry>
</row> </row>
@ -845,9 +844,9 @@ SELECT jdoc-&gt;'guid', jdoc-&gt;'name' FROM api WHERE jdoc @&gt; '{"tags": ["qu
</entry> </entry>
<entry> <entry>
<para> <para>
Same as <literal>.**</literal>, but with a filter over nesting Like <literal>.**</literal>, but selects only the specified
levels of JSON hierarchy. Nesting levels are specified as integers. levels of the JSON hierarchy. Nesting levels are specified as integers.
Zero level corresponds to the current object. To access the lowest Level zero corresponds to the current object. To access the lowest
nesting level, you can use the <literal>last</literal> keyword. nesting level, you can use the <literal>last</literal> keyword.
This is a <productname>PostgreSQL</productname> extension of This is a <productname>PostgreSQL</productname> extension of
the SQL/JSON standard. the SQL/JSON standard.
@ -874,7 +873,7 @@ SELECT jdoc-&gt;'guid', jdoc-&gt;'name' FROM api WHERE jdoc @&gt; '{"tags": ["qu
<para> <para>
The specified <replaceable>index</replaceable> can be an integer, as The specified <replaceable>index</replaceable> can be an integer, as
well as an expression returning a single numeric value, which is well as an expression returning a single numeric value, which is
automatically cast to integer. Zero index corresponds to the first automatically cast to integer. Index zero corresponds to the first
array element. You can also use the <literal>last</literal> keyword array element. You can also use the <literal>last</literal> keyword
to denote the last array element, which is useful for handling arrays to denote the last array element, which is useful for handling arrays
of unknown length. of unknown length.