Re: "an SQL" vs. "a SQL"
Andrew Dunstan <andrew@dunslane.net>
From: Andrew Dunstan <andrew@dunslane.net>
To: Tom Lane <tgl@sss.pgh.pa.us>, Gavin Flower <GavinFlower@archidevsys.co.nz>
Cc: Isaac Morland <isaac.morland@gmail.com>,
David Rowley <dgrowleyml@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-10T21:39:00Z
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 6/10/21 5:32 PM, Tom Lane wrote: > Gavin Flower <GavinFlower@archidevsys.co.nz> writes: >> On 11/06/21 8:17 am, Isaac Morland wrote: >>> ... But then there is "an historic occasion" so go figure. >> The 'h' in 'historic' is silent, at least it used to be -- I think now >> it is almost silent. So using 'an historic occasion' is correct. > It's silent according to the Brits, I believe. In America, the > pronunciation varies. > > I suspect "an historic" is bordering on archaic even in the UK these days. cheers andrew -- Andrew Dunstan EDB: https://www.enterprisedb.com