| From: | Erik Wienhold <ewie(at)ewie(dot)name> |
|---|---|
| To: | David Rowley <dgrowleyml(at)gmail(dot)com> |
| Cc: | pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Use uppercase keywords in foreign key tutorial |
| Date: | 2025-11-06 22:48:41 |
| Message-ID: | 438f7b4e-3855-4598-b857-20cd7fb3df82@ewie.name |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On 2025-11-06 04:06 +0100, David Rowley wrote:
> 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
Thank you, David!
--
Erik Wienhold
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daisuke Higuchi | 2025-11-07 01:40:48 | doc: Fix missing or duplicate closing parentheses in some documents |
| Previous Message | David Rowley | 2025-11-06 03:06:01 | Re: Use uppercase keywords in foreign key tutorial |