| From: | David Rowley <dgrowleyml(at)gmail(dot)com> |
|---|---|
| To: | Erik Wienhold <ewie(at)ewie(dot)name> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <bruce(at)momjian(dot)us>, Nathan Bossart <nathandbossart(at)gmail(dot)com>, Euler Taveira <euler(at)eulerto(dot)com>, pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Use uppercase keywords in foreign key tutorial |
| Date: | 2025-11-06 03:06:01 |
| Message-ID: | CAApHDvokYxXGORORfF_uP2PbaF-UagV-m3yySOfjzuqrVmWkCg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Thu, 6 Nov 2025 at 07:09, Erik Wienhold <ewie(at)ewie(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Erik Wienhold | 2025-11-06 22:48:41 | Re: Use uppercase keywords in foreign key tutorial |
| Previous Message | Erik Wienhold | 2025-11-05 18:09:28 | Re: Use uppercase keywords in foreign key tutorial |