| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | benkoshy(at)hotmail(dot)com, pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Comparison Predicates - example - documentation seems contradictory? |
| Date: | 2022-10-07 10:19:17 |
| Message-ID: | 20221007101917.3hturo5a7v25cjh7@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On 2022-Oct-06, PG Doc comments form wrote:
> See the heading: "Table 9.2. Comparison Predicates"
>
> "2 BETWEEN 3 AND 1 → f" # ok this is false.
>
> But let's read the example immediately below (the 'not between' example)
>
> 2 NOT BETWEEN 1 AND 3 → f # what? This is also false. how can the negation
> also be the same value? I would expect it to be true?
Actually, 2 *is* between 1 and 3. So if you ask if it's NOT between,
that's false.
The other one is false because the boundaries are reversed, and BETWEEN
does not put them in the proper order before comparing. BETWEEN
SYMMETRIC does that, as explained in the line below.
--
Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2022-10-07 13:35:49 | Re: SQL-standard function bodies and creating SECURITY DEFINER routines securely |
| Previous Message | Erki Eessaar | 2022-10-07 08:05:36 | Re: SQL-standard function bodies and creating SECURITY DEFINER routines securely |