Re: JSONB operator unanticipated behaviour - Mailing list pgsql-general

From Adrian Klaver
Subject Re: JSONB operator unanticipated behaviour
Date
Msg-id 8e946df1-ae6a-c9c6-8e99-942923dae6f2@aklaver.com
Whole thread Raw
In response to Re: JSONB operator unanticipated behaviour  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
On 5/18/23 09:36, Tom Lane wrote:
> Adrian Klaver <adrian.klaver@aklaver.com> writes:
>> On 5/18/23 08:46, Tom Lane wrote:
>>> You seem to be reading some fairly old version of the documentation.
>>> The extended definition that Adrian mentions has been there for
>>> awhile, but the JSON operator table didn't link to it before v13.
>>> (I agree that the "top level" bit was just wrong, but it's gone.)
> 
>> Can you elaborate on gone and/or wrong as I see it in the 15 and devel
>> documentation.
> 
> In v12 (and probably earlier, didn't look) Table 9.45 defines @> as
> "Does the left JSON value contain the right JSON path/value entries
> at the top level?" [1].

Alright I get it now.

> 
>             regards, tom lane
> 
> [1] https://www.postgresql.org/docs/12/functions-json.html

-- 
Adrian Klaver
adrian.klaver@aklaver.com




pgsql-general by date:

Previous
From: "Arora, Nick"
Date:
Subject: Unrecognized Node Type Warning
Next
From: Ron
Date:
Subject: Re: Would PostgreSQL 16 native transparent data encryption support database level encryption?