Re: Document that jsonpath == can be used as ANY

From: Marcos Pegoraro <marcos(at)f10(dot)com(dot)br>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Document that jsonpath == can be used as ANY
Date: 2026-09-30 20:21:29
Message-ID: CAB-JLwZeu=oX-D5AXcg=v9p9w+jODOBFJUBkD4PWyeiS3gTPew@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Em qua., 30 de set. de 2026 às 16:14, David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> escreveu:

> I feel like simply including an example here is insufficient. There isn't
> anything special about == going on here;
>

Yes, I agree that an example only is insufficient.
But the behavior of == is indeed different when it's an array or a scalar
value.
It will only work as an array only if assigned to a parameter, and a scalar
works the same way for both.

regards
Marcos

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Narayanan Venkateswaran 2026-09-30 20:58:33 Re: Use instr_time for pg_stat_database block read/write time counters
Previous Message Aleksander Alekseev 2026-09-30 20:15:07 Re: Open SSI correctness issues