| From: | PG Doc comments form <noreply(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-docs(at)lists(dot)postgresql(dot)org |
| Cc: | t(dot)kitynski(at)gmail(dot)com |
| Subject: | Suggestion for deprecated spellings |
| Date: | 2023-01-26 12:19:29 |
| Message-ID: | 167473556945.2667294.2003897901995802549@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/12/sql-createrole.html
Description:
From time to time some spelling for given command gets obsolete, yet it is
shown in the syntax on "equal rights" as other valid clauses. For instance
see `CREATE ROLE` with deprecated spellings like `IN GROUP` or `USER`. I
guess it would be useful to see those spellings visually marked as
deprecated in Synopsis section (with e.g. strike-through or whatever suits
better). Otherwise, when consulting documentation, it often requires jumping
from the synopsis to detailed description and back to check if given
spelling is still applicable. Just a thought. :-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2023-01-26 16:34:55 | Re: Not an error but a difficult wording |
| Previous Message | Laurenz Albe | 2023-01-26 04:49:47 | Re: Not an error but a difficult wording |