Typo in DATATYPE-JSONPATH

From: PG Doc comments form <noreply(at)postgresql(dot)org>
To: pgsql-docs(at)lists(dot)postgresql(dot)org
Cc: kanobt61(at)gmail(dot)com
Subject: Typo in DATATYPE-JSONPATH
Date: 2021-04-15 20:04:24
Message-ID: 161851706474.691.5311470676483994129@wrigleys.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

The following documentation comment has been logged on the website:

Page: https://www.postgresql.org/docs/13/datatype-json.html
Description:

Hello,

On the DATATYPE-JSONPATH page:
https://www.postgresql.org/docs/13/datatype-json.html#DATATYPE-JSONPATH

There is a line that shows that GIN indexes support `@@` and `(at)?` operators
for json matching, then there are two examples trying to show both
operators. However both examples use the `@@` operator.

Examples from the doc:

SELECT jdoc->'guid', jdoc->'name' FROM api WHERE jdoc @@ '$.tags[*] ==
"qui"';
SELECT jdoc->'guid', jdoc->'name' FROM api WHERE jdoc @@ '$.tags[*] ? (@ ==
"qui")';

I think the second example should be using the `(at)?` operator so that both
sample queries do the same thing but with the different operator types. So
the second example should read:

SELECT jdoc->'guid', jdoc->'name' FROM api WHERE jdoc @? '$.tags[*] ? (@ ==
"qui")';

Thank you,
Ben

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Michael Paquier 2021-04-16 01:20:17 Re: INCLUDING COMPRESSION
Previous Message Fujii Masao 2021-04-15 14:24:07 Re: INCLUDING COMPRESSION