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

From David G. Johnston
Subject Re: BUG #14016: Incomplete documentation of IN subquery expression
Date
Msg-id CAKFQuwaXptTZ4Ts1iCXwt2UOxGnBcK+uSbToEj+aTbZfos0Apg@mail.gmail.com
Whole thread Raw
In response to Re: BUG #14016: Incomplete documentation of IN subquery expression  (Bruce Momjian <bruce@momjian.us>)
Responses Re: BUG #14016: Incomplete documentation of IN subquery expression
List pgsql-bugs
On Tuesday, April 26, 2016, Bruce Momjian <bruce@momjian.us> wrote:

> 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
> <javascript:;>> 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?
> >
> >
> > =E2=80=8BI'd append "scalar" to the id to distinguish in from the subqu=
ery
> 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 technical=
ly
> > neither.=E2=80=8B
> >
> > =E2=80=8B<sect2 id=3D"functions-comparisons-in-scalar"> [...]=E2=80=8B
> >
> > [...] rely on the =E2=80=8B<link
> linkend=3D"functions-comparison-in-scalar">array</link>
> > form of [...]=E2=80=8B
>
> Sorry, there was already a link in that place --- I had linked to the
> wrong spot.  New patch attached.
>
>
I think the spot you linked to the first time was correct.  The subquery
form is the one you get when using values, the scalar version is the one
the note wants to link to.

David J.

pgsql-bugs by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: BUG #14016: Incomplete documentation of IN subquery expression
Next
From: Bruce Momjian
Date:
Subject: Re: BUG #14016: Incomplete documentation of IN subquery expression