Commit dfd79e2d authored by Alexander Korotkov's avatar Alexander Korotkov

Fix description for $varname jsonpath variable

The description is ended part way and PASSING clause is not implemented yet.
But the variables might be passed as parameters to several jsonpath functions.
So, complete the description based on the current implementation, leaving
description of PASSING clause in TODO.

Discussion: https://postgr.es/m/CAKPRHz%2BxOuQSSvkuB1mCQjedd%2BB2B1Vnkrq0E-pLmoXyTO%2Bz9Q%40mail.gmail.com
Author: Kyotaro Horiguchi, Alexander Korotkov
parent 1ff8dc9f
...@@ -733,10 +733,12 @@ SELECT jdoc->'guid', jdoc->'name' FROM api WHERE jdoc @> '{"tags": ["qu ...@@ -733,10 +733,12 @@ SELECT jdoc->'guid', jdoc->'name' FROM api WHERE jdoc @> '{"tags": ["qu
</row> </row>
<row> <row>
<entry><literal>$varname</literal></entry> <entry><literal>$varname</literal></entry>
<entry>A named variable. Its value must be set in the <entry>
<command>PASSING</command> clause of an SQL/JSON query function. A named variable. Its value can be set by the parameter
<!-- TBD: See <xref linkend="sqljson-input-clause"/> --> <parameter>vars</parameter> of several JSON processing functions.
for details. See <xref linkend="functions-json-processing-table"/> and
its notes for details.
<!-- TODO: describe PASSING clause once implemented !-->
</entry> </entry>
</row> </row>
<row> <row>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment