| 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-04 02:09:56 |
| Message-ID: | CAApHDvqSiqmZbdDpZ_JhL5TbXNvKCLt1-Wk5j=4uRPoV0hd9hQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Tue, 4 Nov 2025 at 13:04, Erik Wienhold <ewie(at)ewie(dot)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.
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Erik Wienhold | 2025-11-05 18:09:28 | Re: Use uppercase keywords in foreign key tutorial |
| Previous Message | Erik Wienhold | 2025-11-04 00:04:38 | Re: Use uppercase keywords in foreign key tutorial |