Re: "an SQL" vs. "a SQL"
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: David Rowley <dgrowleyml@gmail.com>
Cc: Alvaro Herrera <alvherre@alvh.no-ip.org>,
PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>
Date: 2021-06-10T15:24:16Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Doc: use "an SQL" consistently rather than "a SQL"
- a78cf591a3f5 19 (unreleased) landed
- d866f0374ca6 16.0 landed
- 7bdd489d3d32 15.0 landed
-
Doc: use "an SQL" instead of "a SQL"
- b1b13d2b524e 17.0 landed
-
Use the correct article for abbreviations
- 04539e73faaa 14.0 landed
David Rowley <dgrowleyml@gmail.com> writes: > On Fri, 11 Jun 2021 at 02:53, Tom Lane <tgl@sss.pgh.pa.us> wrote: >> Indeed. I think this is entirely pointless; there's zero hope that >> any consistency you might establish right now will persist very long. > hmm. Yet we do have other standards which we do manage to maintain. If there were some semblance of an overall consensus on the spelling, I'd be fine with weeding out the stragglers. But when the existing usages are only about 2-to-1 in one direction or the other, I feel quite confident in predicting that incoming patches are often going to get this wrong. Especially so if the convention you want to establish in the docs is contrary to the majority usage in the code comments --- how is that not going to confuse people? regards, tom lane