Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oOjyr-0002z5-B8 for pgsql-docs@arkaria.postgresql.org; Thu, 18 Aug 2022 18:10:57 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1oOjyq-0001Z5-4F for pgsql-docs@arkaria.postgresql.org; Thu, 18 Aug 2022 18:10:56 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oOjyp-0001Yv-TG for pgsql-docs@lists.postgresql.org; Thu, 18 Aug 2022 18:10:55 +0000 Received: from momjian.us ([72.94.173.45]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oOjyn-0004A2-CE for pgsql-docs@lists.postgresql.org; Thu, 18 Aug 2022 18:10:55 +0000 Received: from bruce by momjian.us with local (Exim 4.94.2) (envelope-from ) id 1oOjyi-004ioq-Nt; Thu, 18 Aug 2022 14:10:48 -0400 Date: Thu, 18 Aug 2022 14:10:48 -0400 From: Bruce Momjian To: "David G. Johnston" Cc: Tom Lane , Drew DeVault , Pg Docs Subject: Re: [PATCH] doc/queries.sgml: add missing comma Message-ID: References: <20211018091720.31299-1-sir@cmpwn.com> <2007662.1634679184@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="2FU0e43EYuZ4xWz7" Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --2FU0e43EYuZ4xWz7 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit On Tue, Oct 19, 2021 at 06:41:54PM -0700, David G. Johnston wrote: > On Tue, Oct 19, 2021 at 2:33 PM Tom Lane wrote: > > Drew DeVault writes: > > Minor grammatical fix. > > Hmm, I'm not sure that reads any better than before. > > >      > > -    Strictly speaking, this process is iteration not recursion, but > > +    Strictly speaking, this process is iteration, not recursion, but > >      RECURSIVE is the terminology chosen by the SQL > standards > > ... although I think this text is mine, so naturally I'd think > that.  Anyone else have an opinion? > > > > If I read that aloud to myself there is a comma after iteration. > > That said, given that a comma and a "but" later we use the word "RECURSIVE" the > clarification that the process isn't recursion seems redundant.  If one knows > what it means to be "recursive" then they will understand the juxtaposition of > "iteration" and "recursive" just fine.  If they do not, I don't think adding > the word "recursion" is going to make much difference. > > Thus: > Strictly speaking, this process is iteration, but RECURSIVE > is the terminology chosen by the SQL standards committee." > > Because the above sounds just fine, I'd argue that if one does leave "not > recursion" it should be set off by a comma. I went with new wording, which should make this even clearer; patch attached. -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com Indecision is a decision. Inaction is an action. Mark Batterson --2FU0e43EYuZ4xWz7 Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="recursion.diff" diff --git a/doc/src/sgml/queries.sgml b/doc/src/sgml/queries.sgml index 516fbcbf37..51b752709e 100644 --- a/doc/src/sgml/queries.sgml +++ b/doc/src/sgml/queries.sgml @@ -2172,7 +2172,7 @@ SELECT sum(n) FROM t; - Strictly speaking, this process is iteration not recursion, but + Strictly speaking, this process is iterative, not recursive, but RECURSIVE is the terminology chosen by the SQL standards committee. --2FU0e43EYuZ4xWz7--