Re: Use uppercase keywords in foreign key tutorial

Peter Eisentraut <peter@eisentraut.org>

From: Peter Eisentraut <peter@eisentraut.org>
To: jian he <jian.universality@gmail.com>, David Rowley <dgrowleyml@gmail.com>
Cc: Erik Wienhold <ewie@ewie.name>, 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-11T13:12:31Z
Lists: pgsql-docs
On 10.11.25 04:15, jian he wrote:
> On Thu, Nov 6, 2025 at 11:06 AM David Rowley <dgrowleyml@gmail.com> wrote:
>>
>> I reviewed this and double checked you left "uPDaTE" in [1]. Found no
>> issues, so pushed.
>>
> 
> hi.
> 
> in doc/src/sgml/func/func-matching.sgml
> 
> <synopsis>
> substring(<replaceable>string</replaceable> similar
> <replaceable>pattern</replaceable> escape
> <replaceable>escape-character</replaceable>)
> </synopsis>
>      or using the now obsolete SQL:1999 syntax:
> <synopsis>
> substring(<replaceable>string</replaceable> from
> <replaceable>pattern</replaceable> for
> <replaceable>escape-character</replaceable>)
> </synopsis>
>      or as a plain three-argument function:
> <synopsis>
> substring(<replaceable>string</replaceable>,
> <replaceable>pattern</replaceable>,
> <replaceable>escape-character</replaceable>)
> </synopsis>
> 
> key word: "similar", "escape", "from", "for" within the above synopsis
> section need uppercase too?

I don't think that would be a good change.  substring is also a keyword, 
but it was said not to upper-case keywords used as functions.  So in my 
mind that should also apply to other syntax elements of function-like calls.




Commits

  1. Doc: more uppercase keywords in SQLs

  2. Doc: use uppercase keywords in SQLs