Re: Ambiguity in VALUES synopsis: LIMIT vs FETCH
| От | David G. Johnston |
|---|---|
| Тема | Re: Ambiguity in VALUES synopsis: LIMIT vs FETCH |
| Дата | |
| Msg-id | CAKFQuwYmNY98SiUc8PQMq5iEGDq4EbeoXC4M9A+Co11RAPKOow@mail.gmail.com обсуждение исходный текст |
| Ответ на | Ambiguity in VALUES synopsis: LIMIT vs FETCH (Cheng Ding <cheng.ding@utexas.edu>) |
| Список | pgsql-docs |
On Tuesday, August 26, 2025, Cheng Ding <cheng.ding@utexas.edu> wrote:
Hello docs team,
I believe there’s an ambiguity in the
VALUEScommand synopsis that can mislead readers into thinkingLIMITandFETCHcan be used together.…
Alternatively, add a short note right under the synopsis:
Note:
FETCH { FIRST | NEXT } … ONLYis an alternative toLIMITand cannot be used together with it.
The final paragraph in description explains the either-or nature of limit/fetch. It also directs the user to the Select page for more details. And the comparability section also explains that fetch is standard while limit is PostgresSQL-specific.
IMO the choice of representation here is acceptable. The redundancy should be a big tell even if you don’t read the docs carefully. And hopefully whatever source you actually learn about the feature from covers the material well and this quick reference page is just a reminder that both exist.
David J.
В списке pgsql-docs по дате отправления: