aboutsummaryrefslogtreecommitdiff
path: root/src/backend/utils/adt/jsonpath_exec.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2024-01-25 11:32:18 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2024-01-25 11:32:18 -0500
commit7014c9a4bba2d1b67d60687afb5b2091c1d07f73 (patch)
treeb5bf7a5ccd54b1c2ce99f7202e0f9f4f56396491 /src/backend/utils/adt/jsonpath_exec.c
parent66ea94e8e606529bb334515f388c62314956739e (diff)
downloadpostgresql-7014c9a4bba2d1b67d60687afb5b2091c1d07f73.tar.gz
postgresql-7014c9a4bba2d1b67d60687afb5b2091c1d07f73.zip
Doc: improve documentation for jsonpath behavior.
Clarify the behavior of jsonpath operators and functions by describing their two different modes of operation explicitly. In addition to the SQL-spec behavior, where a path returns a list of matching items, we have a "predicate check" form that always returns a single boolean result. That was mentioned in only one place, but it seems better to annotate each operator and function as to which form(s) it takes. Also improve the examples by converting them into actual executable SQL with results, and do a bunch of incidental wordsmithing. David Wheeler, reviewed by Erik Wienhold, Jian He, and myself Discussion: https://postgr.es/m/7262A188-59CA-4A8A-AAD7-83D4FF0B9758@justatheory.com
Diffstat (limited to 'src/backend/utils/adt/jsonpath_exec.c')
0 files changed, 0 insertions, 0 deletions