Received: from malur.postgresql.org ([2a02:16a8:dc51::56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1gC5n9-0006Au-0B for pgsql-docs@arkaria.postgresql.org; Mon, 15 Oct 2018 16:32:27 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gC5n7-0003xp-D4 for pgsql-docs@arkaria.postgresql.org; Mon, 15 Oct 2018 16:32:25 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1gC5n7-0003xi-4N for pgsql-docs@lists.postgresql.org; Mon, 15 Oct 2018 16:32:25 +0000 Received: from momjian.us ([72.94.173.45]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gC5n4-0003xY-JI for pgsql-docs@lists.postgresql.org; Mon, 15 Oct 2018 16:32:23 +0000 Received: from bruce by momjian.us with local (Exim 4.84_2) (envelope-from ) id 1gC5n2-0001YK-Pr; Mon, 15 Oct 2018 12:32:20 -0400 Date: Mon, 15 Oct 2018 12:32:20 -0400 From: Bruce Momjian To: "David G. Johnston" Cc: KES , "pgsql-docs@lists.postgresql.org" Subject: Re: Ambiguous usage of 'any' in explanation Message-ID: <20181015163220.GA18438@momjian.us> References: <153701242703.22334.1476830122267077397@wrigleys.postgresql.org> <20181011210934.GG7807@momjian.us> <5831541539340923@iva8-3af116a85b74.qloud-c.yandex.net> <20181012150433.GA12966@momjian.us> <1806231539422738@sas1-00d5718ef836.qloud-c.yandex.net> <20181013173148.GA25417@momjian.us> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Sun, Oct 14, 2018 at 11:00:18PM -0700, David G. Johnston wrote: > On Saturday, October 13, 2018, Bruce Momjian wrote: > > On Sat, Oct 13, 2018 at 12:25:38PM +0300, KES wrote: > > >or NULL if any of the comparisons result in unknown > > result in unknown?? > > Well, SQL has a three-valued logic, and UNKOWN values are treated like > NULL.  For me they have always been the same, and I would like to avoid > "unknown" in this context, if possible. > > > > I was just trying to avoid using the word null twice in the same sentence but > it’s not a strong aversion. I am thinking of applying my earlier patch and calling it done. -- Bruce Momjian http://momjian.us EnterpriseDB http://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Ancient Roman grave inscription +