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

Michael Paquier <michael@paquier.xyz>

From: Michael Paquier <michael@paquier.xyz>

To: Geoff Winkless <pgsqladmin@geoff.dj>

Cc: Alvaro Herrera <alvherre@alvh.no-ip.org>, David Rowley <dgrowleyml@gmail.com>, PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>

Date: 2021-06-13T11:13:07Z

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 Sun, Jun 13, 2021 at 07:36:54AM +0100, Geoff Winkless wrote:
> On Thu, 10 Jun 2021, 15:35 Alvaro Herrera, <alvherre@alvh.no-ip.org> wrote:
>> src/backend/libpq/auth.c:847:    * has.  If it's an MD5 hash, we must do
>> MD5 authentication, and if it's a
>> src/backend/libpq/auth.c:848:    * SCRAM secret, we must do SCRAM
>> authentication.
> 
> Not sure whether you were just listing examples and you weren't suggesting
> this should be changed, but surely "SCRAM" is pronounced "scram" and is
> thus "a SCRAM"?

RFC 5802 uses "a SCRAM something" commonly, but "a SCRAM" alone does
not make sense:
https://datatracker.ietf.org/doc/html/rfc5802

The sentences quoted above look fine to me.
--
Michael