From: | PG Doc comments form <noreply(at)postgresql(dot)org> |
---|---|
To: | pgsql-docs(at)lists(dot)postgresql(dot)org |
Cc: | kes-kes(at)yandex(dot)ru |
Subject: | Ambiguous usage of 'any' in explanation |
Date: | 2018-09-15 11:53:47 |
Message-ID: | 153701242703.22334.1476830122267077397@wrigleys.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/10/static/functions-subquery.html
Description:
Hi.
The [DOC](https://www.postgresql.org/docs/10/static/functions-subquery.html)
says:
The result is NULL if the comparison does not return false for any
subquery row
does *any* mean here: some or all?
For example in
[MySQL](https://dev.mysql.com/doc/refman/8.0/en/any-in-some-subqueries.html)
I have found this explanation:
>Use of the word SOME is rare, but this example shows why it might be
useful. To most people, the English phrase “a is not equal to any b” means
“there is no b which is equal to a,” but that is not what is meant by the
SQL syntax. The syntax means “there is some b to which a is not equal.”
Using <> SOME instead helps ensure that everyone understands the true
meaning of the query.
From | Date | Subject | |
---|---|---|---|
Next Message | Adrien NAYRAT | 2018-09-18 10:32:54 | Mention FK creation take ShareRowExclusiveLock on referenced table |
Previous Message | PG Doc comments form | 2018-09-13 15:14:08 | effective_cache_size |