Re: BUG #14016: Incomplete documentation of IN subquery expression - Mailing list pgsql-bugs

From Bruce Momjian
Subject Re: BUG #14016: Incomplete documentation of IN subquery expression
Date
Msg-id 20160427002010.GC13058@momjian.us
Whole thread Raw
In response to Re: BUG #14016: Incomplete documentation of IN subquery expression  ("David G. Johnston" <david.g.johnston@gmail.com>)
Responses Re: BUG #14016: Incomplete documentation of IN subquery expression
List 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@momjian.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@momjian.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

pgsql-bugs by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: BUG #14016: Incomplete documentation of IN subquery expression
Next
From: "David G. Johnston"
Date:
Subject: Re: BUG #14016: Incomplete documentation of IN subquery expression