Re: BUG #14016: Incomplete documentation of IN subquery expression

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: Manlio Perillo <manlio(dot)perillo(at)gmail(dot)com>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #14016: Incomplete documentation of IN subquery expression
Date: 2016-04-27 00:20:10
Message-ID: 20160427002010.GC13058@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, Apr 26, 2016 at 02:00:39PM -0700, David G. Johnston wrote:
> On Tue, Apr 26, 2016 at 1:27 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> > >>>Note: This form of IN is not truly a subquery expression, but it seems
> best
> > to document it in the same place as subquery IN.
>
> Does the attached patch improve this?
>
>
> ​I'd append "scalar" to the id to distinguish in from the subquery version. 
> Otherwise any suggest I make seems like overkill.  The main point being the
> "list of scalars" is not a term we use on the referenced page, and the chapter
> header indicates "Row and Array" of which this is similar but technically
> neither.​
>
> ​<sect2 id="functions-comparisons-in-scalar"> [...]​
>
> [...] rely on the ​<link linkend="functions-comparison-in-scalar">array</link>
> form of [...]​

Sorry, there was already a link in that place --- I had linked to the
wrong spot. New patch attached.

--
Bruce Momjian <bruce(at)momjian(dot)us> 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 +

Attachment Content-Type Size
in.diff text/x-diff 917 bytes

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message David G. Johnston 2016-04-27 00:32:04 Re: BUG #14016: Incomplete documentation of IN subquery expression
Previous Message Andres Freund 2016-04-26 21:32:07 Re: [BUGS] Breakage with VACUUM ANALYSE + partitions