Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1vEDfv-007gmT-SU for pgsql-docs@arkaria.postgresql.org; Wed, 29 Oct 2025 21:25:47 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1vEDfu-003p0n-Sz for pgsql-docs@arkaria.postgresql.org; Wed, 29 Oct 2025 21:25:45 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1vEDfu-003p0e-Lt for pgsql-docs@lists.postgresql.org; Wed, 29 Oct 2025 21:25:45 +0000 Received: from momjian.us ([72.94.173.45]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vEDfs-004S59-0O for pgsql-docs@lists.postgresql.org; Wed, 29 Oct 2025 21:25:44 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=momjian.us; s=2025010100; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID: Subject:Cc:To:From:Date:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description; bh=6/l3qcQrv5QqdvoLpIr8IEX5YpmN8Mfb2yu9wViuGkk=; b=jnc41 sYlz2S8yAwrEAAcEs1b+WahuaVuD5J3eMmYIK2CDZ4xnjox3Pm6B23Zaa56Bktu7oY5183bMCP6JQ gm6hT4wPGwcmX5TpSZ42bPgSQRS9bIV1PoYZ7vKM4uzeynC0WMab6dSYNiz0TgD/11c6gGpQchVXn O16ZsY9BrptHd5gsNGc5XBTPUBqPGr/vq0lKd6U8WeHloWyPDGjzVG/X7h7kXQAYRQrrSpeDiSCAj 2w1wz+fzOmBbUtmOU3T1+gaUvXk+r6EFZyaD/rKPf01nXVCFXAl23X+kZUFG22GQFernA+HC9UMLx R2NoSq3dE3+VeKSEiv91ejFqccRlg==; Received: from bruce by momjian.us with local (Exim 4.98.2) (envelope-from ) id 1vEDfr-00000000fAs-147g; Wed, 29 Oct 2025 17:25:43 -0400 Date: Wed, 29 Oct 2025 17:25:43 -0400 From: Bruce Momjian To: David Rowley Cc: Tom Lane , Nathan Bossart , Euler Taveira , Erik Wienhold , pgsql-docs@lists.postgresql.org Subject: Re: Use uppercase keywords in foreign key tutorial Message-ID: References: <82eb512b-8ed2-46be-b311-54ffd26978c4@ewie.name> <0a9d7393-1cf2-4d38-a648-631c1f93e345@ewie.name> <2903384.1761770924@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Thu, Oct 30, 2025 at 10:24:30AM +1300, David Rowley wrote: > On Thu, 30 Oct 2025 at 09:48, Tom Lane wrote: > > > > Bruce Momjian writes: > > > On Tue, Oct 28, 2025 at 04:34:45PM -0500, Nathan Bossart wrote: > > >> I noticed the patch also changes some column types to lowercase: > > >> ... > > >> - category_N TEXT > > >> + category_N text > > >> > > >> FWIW I tend to use uppercase for those, too, but I'm not sure there is a > > >> preferred style for the docs. > > > > > Agreed, uppercase is better for type names. > > > > "text" is not a keyword according to either us or the SQL standard. > > I agree that there's some reason to capitalize things that are > > grammar keywords, such as INTEGER or VARCHAR, but it's a big stretch > > to go from that to capitalizing everything that is a type name. > > Would you capitalize user-defined type names? > > Going by: git grep -i "\btext\b," we're fairly consistently using > lower case, so FWIW, when I looked, I thought Eric's change made > sense. > > How about if Eric just drops the portion of the patch that alters the > casing of the types and leaves all the keyword uppercasing stuff in. > Any objections to that part? Works for me. -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com Do not let urgent matters crowd out time for investment in the future.