Re: Use uppercase keywords in foreign key tutorial
David Rowley <dgrowleyml@gmail.com>
From: David Rowley <dgrowleyml@gmail.com>
To: Erik Wienhold <ewie@ewie.name>
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-06T03:06:01Z
Lists: pgsql-docs
On Thu, 6 Nov 2025 at 07:09, Erik Wienhold <ewie@ewie.name> wrote: > > On 2025-11-04 03:09 +0100, David Rowley wrote: > > 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. I reviewed this and double checked you left "uPDaTE" in [1]. Found no issues, so pushed. Thank you. David [1] https://www.postgresql.org/docs/current/sql-syntax-lexical.html
Commits
-
Doc: more uppercase keywords in SQLs
- 812367f3d487 19 (unreleased) landed
-
Doc: use uppercase keywords in SQLs
- 49d43faa835f 19 (unreleased) landed