Re: BUG #13967: Documentation. Plpgsql 'execute' description
От | David G. Johnston |
---|---|
Тема | Re: BUG #13967: Documentation. Plpgsql 'execute' description |
Дата | |
Msg-id | CAKFQuwaA1EW6OFvOoXJVj+-z4HJBajoStG_f2ha1XDoiBRVKUQ@mail.gmail.com обсуждение исходный текст |
Ответ на | BUG #13967: Documentation. Plpgsql 'execute' description (iurii.i.popov@gmail.com) |
Список | pgsql-bugs |
On Wed, Feb 17, 2016 at 8:11 AM, <iurii.i.popov@gmail.com> wrote: > The following bug has been logged on the website: > > Bug reference: 13967 > Logged by: Iurii Popov > Email address: iurii.i.popov@gmail.com > PostgreSQL version: 9.5.1 > Operating system: Ubuntu > Description: > > At > > http://www.postgresql.org/docs/9.5/static/plpgsql-statements.html#PLPGSQL= -STATEMENTS-EXECUTING-DYN > > you can see > > If multiple rows are returned, only the first will be assigned to the INT= O > variable. > > It will be useful to write information from (or a link to) > > http://www.postgresql.org/docs/9.5/static/plpgsql-control-structures.html= #AEN62513 > > about RETURN QUERY EXECUTE statement to return set of rows. > The former (returning a value into a internally defined variable) is separate from the second (returning a value to outside =E2=80=8Bthe functio= n). While they do have some relation to each other - namely the former can be used to set variables that are then externally returned - that seems insufficient. But, maybe I'm too familiar with this. Maybe a more detailed suggestion would make the need more clear. In any case this seems to be quite far from being a bug. There is a pgsql-docs list where suggestions like this are better posted. David J.
В списке pgsql-bugs по дате отправления: