Re: Use uppercase keywords in foreign key tutorial
Erik Wienhold <ewie@ewie.name>
From: Erik Wienhold <ewie@ewie.name>
To: David Rowley <dgrowleyml@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Bruce Momjian <bruce@momjian.us>, Nathan Bossart <nathandbossart@gmail.com>, Euler Taveira <euler@eulerto.com>, pgsql-docs@lists.postgresql.org
Date: 2025-11-05T18:09:28Z
Lists: pgsql-docs
Attachments
- v6-0001-doc-Use-uppercase-keywords.patch (text/plain)
On 2025-11-04 03:09 +0100, David Rowley wrote: > On Tue, 4 Nov 2025 at 13:04, Erik Wienhold <ewie@ewie.name> wrote: > > > > On 2025-11-03 23:37 +0100, David Rowley wrote: > > > I'm starting to wonder if adjusting the spacing here is a worthwhile > > > change. > > > > I think it's worth to have that consistency. If the patch is too broad > > I can of course limit it to the listings with inconsistent keyword > > casing which is more less patch v2 plus some changes from v3 and later. > > > > Or just fix the keywords for now to get that out of the way and deal > > with the spacing in a separate patch/thread. > > I think just the keyword upper casing is a good idea for now. I'm > starting to lose hope that there's enough merit and consistency to the > proposed whitespace changes. Maybe there's a subset of it that does > make sense to do. Done in the attached v6. But I kept the few whitespace changes on lines where I change keywords to uppercase. It's mostly a single space after commas in column and parameter lists which I think also enhances readability. -- Erik Wienhold
Commits
-
Doc: more uppercase keywords in SQLs
- 812367f3d487 19 (unreleased) landed
-
Doc: use uppercase keywords in SQLs
- 49d43faa835f 19 (unreleased) landed