Re: BUG #14016: Incomplete documentation of IN subquery expression
От | David G. Johnston |
---|---|
Тема | Re: BUG #14016: Incomplete documentation of IN subquery expression |
Дата | |
Msg-id | CAKFQuwYR0xCbQS=fpv50Jqnsii=Y+B5sgkzzkY_PJG6M5fR1OQ@mail.gmail.com обсуждение исходный текст |
Ответ на | BUG #14016: Incomplete documentation of IN subquery expression (manlio.perillo@gmail.com) |
Ответы |
Re: BUG #14016: Incomplete documentation of IN subquery
expression
|
Список | pgsql-bugs |
On Fri, Mar 11, 2016 at 9:39 AM, <manlio.perillo@gmail.com> wrote: > The following bug has been logged on the website: > > Bug reference: 14016 > Logged by: Manlio Perillo > Email address: manlio.perillo@gmail.com > PostgreSQL version: 9.5.1 > Operating system: Linux > Description: > > At the end of the documentation for VALUE (sql-values.html), there is the > following tip: > "For simple IN tests, it's better to rely on the list-of-scalars form of = IN > than to write a VALUES query as shown above" > > However there is no reference to the "list-of-scalars" forms of IN, in th= e > functions-subquery.html page. It is only reported that the supported > syntax > is "expression IN (subquery)" > > The reference was available in an old version (7.3), where the manual > documented both the scalar form and sub query form: > "expression IN (value[, ...])" > =E2=80=8BIt was moved... =E2=80=8B http://www.postgresql.org/docs/9.5/interactive/functions-comparisons.html#A= EN20283 =E2=80=8BThe interpretation being that a "list of scalars" is, in this situ= ation, semantically equivalent to an array - though having the later you would have to use "=3DANY(array)" instead of "IN" =E2=80=8BApparently someone disagreed with the note in the subquery section= : >>>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. David J.
В списке pgsql-bugs по дате отправления: