Commit70236cf

committed

doc: clarify that jsonb_path_match() returns an SQL boolean

Not a JSON boolean. Also clarify that other predicate check expressionsfunctions return a JSON boolean, not an SQL boolean.Reported-by: jian heDiscussion:https://postgr.es/m/CACJufxH7tP1NXCHN1bUBXcEB=dv7-qE+ZjB3UxwK6Em+9Qzb9Q@mail.gmail.comBackpatch-through: 17

1 parentf722dd3 commit70236cfCopy full SHA for 70236cf

File tree

-4

lines changed

-4

lines changed

Lines changed: 4 additions & 4 deletions

Original file line number	Diff line number	Diff line change
`@@ -17178,8 +17178,8 @@ ERROR: value too long for type character(2)`
`17178`	`17178`	`<returnvalue>boolean</returnvalue>`
`17179`	`17179`	`</para>`
`17180`	`17180`	`<para>`
`17181`		`- Returns the result of a JSON path predicate check for the specified`
`17182`		`- JSON value.`
	`17181`	`+ Returns theSQL booleanresult of a JSON path predicate check`
	`17182`	`+for the specifiedJSON value.`
`17183`	`17183`	`(This is useful only`
`17184`	`17184`	`with <link linkend="functions-sqljson-check-expressions">predicate`
`17185`	`17185`	`check expressions</link>, not SQL-standard JSON path expressions,`
`@@ -17646,9 +17646,9 @@ SELECT '{`
`17646`	`17646`	`Boolean predicate, whereas the SQL standard allows predicates only within`
`17647`	`17647`	`filters. While SQL-standard path expressions return the relevant`
`17648`	`17648`	`element(s) of the queried JSON value, predicate check expressions`
`17649`		`- return the single three-valued result of the`
	`17649`	`+ return the single three-valued<type>jsonb</type>result of the`
`17650`	`17650`	`predicate: <literal>true</literal>,`
`17651`		`- <literal>false</literal>, or <literal>unknown</literal>.`
	`17651`	`+ <literal>false</literal>, or <literal>null</literal>.`
`17652`	`17652`	`For example, we could write this SQL-standard filter expression:`
`17653`	`17653`	`<screen>`
`17654`	`17654`	`<prompt>=></prompt> <userinput>select jsonb_path_query(:'json', '$.track.segments ?(@[*].HR > 130)');</userinput>`

Comments

(0)