BUG #17440: not expected result from jsonb_path_query

From: PG Bug reporting form <noreply(at)postgresql(dot)org>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: edouard(dot)hibon(at)free(dot)fr
Subject: BUG #17440: not expected result from jsonb_path_query
Date: 2022-03-15 16:58:59
Message-ID: 17440-b8f554829089cf0f@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 17440
Logged by: Edouard HIBON
Email address: edouard(dot)hibon(at)free(dot)fr
PostgreSQL version: 14.0
Operating system: windows 10
Description:

Query 1 : SELECT jsonb_path_query('[1,2,3]' :: jsonb, '$') results in 1
value '[1,2,3]' :: jsonb as expected
Query 2 : SELECT jsonb_path_query('[1,2,3]' :: jsonb, '$[*]') results in a
set of 3 values '1', '2', '3' as expected
Query 3 : SELECT jsonb_path_query('[1,2,3]' :: jsonb, '$[*] ? (@ <> null)')
results in a set of 3 values '1', '2', '3' as expected
Query 4 : SELECT jsonb_path_query('[1,2,3]' :: jsonb, '$ ? (@ <> null)')
results in a set of 3 values '1', '2', '3' as for the queries 2 & 3 whereas
I would expect only one value '[1,2,3]' as for the query 1 because there is
no member accessor nor array element accessor in this jsonpath, and @ should
represent the initial jsonb value being queried $

demo :
https://dbfiddle.uk/?rdbms=postgres_14&fiddle=f09164502df5ee1bb620057689e6f810

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2022-03-15 18:33:20 Re: BUG #17439: DROP FUNCTION functionName(); drops associated generated column without using CASCADE
Previous Message PG Bug reporting form 2022-03-15 15:11:17 BUG #17439: DROP FUNCTION functionName(); drops associated generated column without using CASCADE