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

David Rowley <dgrowleyml@gmail.com>

From: David Rowley <dgrowleyml@gmail.com>

To: Andrew Dunstan <andrew@dunslane.net>

Cc: Tom Lane <tgl@sss.pgh.pa.us>, Gavin Flower <GavinFlower@archidevsys.co.nz>, Isaac Morland <isaac.morland@gmail.com>, Daniel Gustafsson <daniel@yesql.se>, Dave Page <dpage@pgadmin.org>, Peter Eisentraut <peter.eisentraut@enterprisedb.com>, PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>

Date: 2021-06-10T23:38:02Z

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

On Fri, 11 Jun 2021 at 09:39, Andrew Dunstan <andrew@dunslane.net> wrote:
> I suspect "an historic" is bordering on archaic even in the UK these days.

Yeah, that's a weird one. Maybe
https://en.wikipedia.org/wiki/H-dropping is to blame.

David