From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
---|---|
To: | David Rowley <dgrowleyml(at)gmail(dot)com>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: "an SQL" vs. "a SQL" |
Date: | 2021-06-10 08:31:37 |
Message-ID: | f4572891-e001-f029-f95b-9440c8cc1509@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 10.06.21 09:26, David Rowley wrote:
> It seems we have no standard as to if we say "a SQL" or "an SQL".
The SQL standard uses "an SQL-something".
> However, we mostly use "an SQL" in the docs.
>
> ~/pg_src$ cd doc/
> ~/pg_src/doc$ git grep -E "\s(a|A)\sSQL\s" | wc -l
> 55
> ~/pg_src/doc$ git grep -E "\s(an|An)\sSQL\s" | wc -l
> 94
>
> I think we should change all 55 instances of "a SQL" in the docs to
> use "an SQL" and leave the 800 other instances of "a SQL" alone.
> Changing those does not seem worthwhile as it could cause
> back-patching pain.
agreed
> Further, there might be a few more in the docs that we might want to
> consider changing:
>
> git grep -E "\sa\s(A|E|F|H|I|L|M|N|O|S|X)[A-Z]{2,5}\s"
>
> I see "a FSM", "a FIFO", "a SSPI", "a SASL", "a MCV", "a SHA", "a SQLDA"
>
> My regex foo is not strong enough to think how I might find multiline instances.
Um, of those, I pronounce FIFO, SASL, and SHA as words, with an "a" article.
From | Date | Subject | |
---|---|---|---|
Next Message | Ajin Cherian | 2021-06-10 08:34:15 | Re: Decoding of two-phase xacts missing from CREATE_REPLICATION_SLOT command |
Previous Message | David Rowley | 2021-06-10 08:14:57 | Re: Fix a few typos in brin_minmax_multi.c |