From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Euler Taveira <euler(at)timbira(dot)com(dot)br> |
Cc: | spam_eater(at)gmx(dot)net, pgsql-docs(at)lists(dot)postgresql(dot)org |
Subject: | Re: Missing documentation for FETCH FIRST in chapter 7.6 |
Date: | 2023-11-17 21:48:23 |
Message-ID: | ZVffp7398eVsjZxj@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On Wed, Jun 13, 2018 at 04:17:55PM -0300, Euler Taveira wrote:
> 2018-05-16 10:22 GMT-03:00 PG Doc comments form <noreply(at)postgresql(dot)org>:
> > The documentation of the SELECT statement lists FETCH FIRST/OFFSET as an
> > alternative to the proprietary LIMIT clause.
> >
> > https://www.postgresql.org/docs/current/static/sql-select.html#SQL-LIMIT
> >
> > However, chapter 7.6 about LIMIT/OFFSET does not mention the alternative.
> >
> > https://www.postgresql.org/docs/current/static/queries-limit.html
> >
> Make sense. I propose the attached patch that adds a link to the LIMIT
> section in the SELECT reference page. I also renamed the "number"
> variables to the same names used in the SELECT reference page and put
> OFFSET in a new line (it looks visually better).
I applied the attached patch based on your patch to master. Thanks.
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
Attachment | Content-Type | Size |
---|---|---|
limit.diff | text/x-diff | 1.1 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2023-11-17 22:13:21 | Re: SELECT ... FOR UPDATE OF clause documentation implies use of table_names rather than aliases |
Previous Message | Tom Lane | 2023-11-16 17:05:02 | Re: Additional Notes |