| From: | "David E(dot) Wheeler" <david(at)justatheory(dot)com> |
|---|---|
| To: | "David E(dot) Wheeler" <david(at)justatheory(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Erik Wienhold <ewie(at)ewie(dot)name>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Patch: Improve Boolean Predicate JSON Path Docs |
| Date: | 2024-01-21 20:02:37 |
| Message-ID: | 43F76952-19A1-4F86-9715-F2F153323CFD@justatheory.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Jan 21, 2024, at 14:58, David E. Wheeler <david(at)justatheory(dot)com> wrote:
> I make this interpretation based on this bit of the docs:
Sorry, that’s from my branch. Here it is in master:
<listitem>
<para>
A path expression can be a Boolean predicate, although the SQL/JSON
standard allows predicates only in filters. This is necessary for
implementation of the <literal>@@</literal> operator. For example,
the following <type>jsonpath</type> expression is valid in
<productname>PostgreSQL</productname>:
<programlisting>
$.track.segments[*].HR < 70
</programlisting>
</para>
</listitem>
In any event, something to do with @@, perhaps to have some compatibility with `jsonb @> jsonb`? I don’t know why @@ was important to have.
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Luzanov | 2024-01-21 21:34:58 | Re: Things I don't like about \du's "Attributes" column |
| Previous Message | David E. Wheeler | 2024-01-21 19:58:10 | Re: Patch: Improve Boolean Predicate JSON Path Docs |