From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | jian he <jian(dot)universality(at)gmail(dot)com> |
Cc: | 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 13:46:51 |
Message-ID: | ZxEVS4erCXiDMkXZ@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Jun 21, 2024 at 10:30:08AM +0800, jian he wrote:
> hi.
> -------------
> 9.16.2.1.1. Boolean Predicate Check Expressions
> As an extension to the SQL standard, a PostgreSQL path expression can
> be a Boolean predicate, whereas the SQL standard allows predicates
> only within filters. While SQL-standard path expressions return the
> relevant element(s) of the queried JSON value, predicate check
> expressions return the single three-valued result of the predicate:
> true, false, or unknown. For example, we could write this SQL-standard
> filter expression:
>
> -------------
> slight inconsistency, "SQL-standard" versus "SQL standard"
> "path expression can be a Boolean predicate", why capital "Boolean"?
I think "SQL-standard" is used with the dash above because it is an
adjective, and without the dash, it might be understood as "SQL
standard-path" vs. "SQL-standard path". There aren't clear rules on
when to add the dash, but when it can be misread, a dash is often added.
--
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?"
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2024-10-17 13:56:30 | Re: doc: virtual envs with Pl/Python |
Previous Message | torikoshia | 2024-10-17 13:45:46 | Add reject_limit option to file_fdw |