Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit dfd79e2

Browse files
committed
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
1 parent 1ff8dc9 commit dfd79e2

File tree

1 file changed

+6
-4
lines changed

1 file changed

+6
-4
lines changed

doc/src/sgml/json.sgml

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -733,10 +733,12 @@ SELECT jdoc->'guid', jdoc->'name' FROM api WHERE jdoc @> '{"tags": ["qu
733733
</row>
734734
<row>
735735
<entry><literal>$varname</literal></entry>
736-
<entry>A named variable. Its value must be set in the
737-
<command>PASSING</command> clause of an SQL/JSON query function.
738-
<!-- TBD: See <xref linkend="sqljson-input-clause"/> -->
739-
for details.
736+
<entry>
737+
A named variable. Its value can be set by the parameter
738+
<parameter>vars</parameter> of several JSON processing functions.
739+
See <xref linkend="functions-json-processing-table"/> and
740+
its notes for details.
741+
<!-- TODO: describe PASSING clause once implemented !-->
740742
</entry>
741743
</row>
742744
<row>

0 commit comments

Comments
 (0)