Re: "an SQL" vs. "a SQL"

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>

To: Alvaro Herrera <alvherre@alvh.no-ip.org>

Cc: David Rowley <dgrowleyml@gmail.com>, PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>

Date: 2021-06-10T14:53:26Z

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

Alvaro Herrera <alvherre@alvh.no-ip.org> writes:
> On 2021-Jun-10, David Rowley wrote:
>> It seems we have no standard as to if we say "a SQL" or "an SQL".

> I was just reading the standard a couple of days ago and happened to
> notice that the standard itself in some places uses "a SQL" and in other
> places "an SQL".  I didn't stop to make an analysis of that, so I don't
> know how prevalent each form is -- I just giggled and moved on.

Indeed.  I think this is entirely pointless; there's zero hope that
any consistency you might establish right now will persist very long.
The largest effect of this proposed patch will be to create
back-patching headaches.

			regards, tom lane