Hello! I noticed an old TODO while reading through the code for the Section 8.14 docs. I've attached a patch below which attempts to resolve it, by adding some more clarification about the PASSING clause, now that it has been implemented.
Specifically, I clarified that jsonpath named variables ($varname) can be set either through the vars parameter or using the PASSING clause. Any feedback is appreciated! Thanks, Adi Gollamudi
>From 1b8a333a9e5476a6d2cc9b9f646be68cdb72dd96 Mon Sep 17 00:00:00 2001 From: Aditya Gollamudi <[email protected]> Date: Fri, 16 Jan 2026 23:38:00 -0500 Subject: [PATCH] Document PASSING clause support for jsonpath variables Resolve a TODO left in doc/src/sgml/json.sgml by clarifying that jsonpath named variables ($varname) can be set by both the vars parameter of the JSON processing functions or the SQL/JSON PASSING clause. Author: Aditya Gollamudi <[email protected]> --- doc/src/sgml/json.sgml | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/doc/src/sgml/json.sgml b/doc/src/sgml/json.sgml index 206eadb8f7b..8a2aad5935e 100644 --- a/doc/src/sgml/json.sgml +++ b/doc/src/sgml/json.sgml @@ -882,9 +882,10 @@ UPDATE table_name SET jsonb_field[1]['a'] = '1'; <entry><literal>$varname</literal></entry> <entry> A named variable. Its value can be set by the parameter - <parameter>vars</parameter> of several JSON processing functions; - see <xref linkend="functions-json-processing-table"/> for details. - <!-- TODO: describe PASSING clause once implemented !--> + <parameter>vars</parameter> of several JSON processing functions + (see <xref linkend="functions-json-processing-table"/>), or by + using the SQL/JSON <literal>PASSING</literal> clause as described + in <xref linkend="sqljson-query-functions"/>. </entry> </row> <row> -- 2.34.1
