| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Marcos Pegoraro <marcos(at)f10(dot)com(dot)br> |
| Cc: | jian he <jian(dot)universality(at)gmail(dot)com>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: minor doc issue in 9.16.2.1.1. Boolean Predicate Check Expressions |
| Date: | 2024-10-17 18:05:02 |
| Message-ID: | ZxFRzpML0FrWUmM5@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Oct 17, 2024 at 02:47:57PM -0300, Marcos Pegoraro wrote:
> Em qui., 17 de out. de 2024 às 13:31, Bruce Momjian <bruce(at)momjian(dot)us>
> escreveu:
>
> Oh, okay, but I think we need to say JSON null so we are clear --- patch
>
>
> But true, false and null are all JSON, since you cannot do
> select jsonb_path_query('{}'::jsonb,'$.track.segments[*].HR > 130') = true;
Obviously, I was confused then. This confirms the result is JSONB:
SELECT pg_typeof(jsonb_path_query('{}'::jsonb,'$.track.segments[*].HR > 130'));
pg_typeof
-----------
jsonb
> So, it would be better to be clear that all possible returned values are JSON,
> no ?
Yes, updated patch attached.
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
When a patient asks the doctor, "Am I going to die?", he means
"Am I going to die soon?"
| Attachment | Content-Type | Size |
|---|---|---|
| json.diff | text/x-diff | 902 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2024-10-17 19:42:41 | Re: ECPG cleanup and fix for clang compile-time problem |
| Previous Message | Alexander Lakhin | 2024-10-17 18:00:00 | Re: ECPG cleanup and fix for clang compile-time problem |