Re: [HACKERS] Re: issue: record or row variable cannot be part ofmultiple-item INTO list
| От | Pavel Stehule |
|---|---|
| Тема | Re: [HACKERS] Re: issue: record or row variable cannot be part ofmultiple-item INTO list |
| Дата | |
| Msg-id | CAFj8pRBVL_NsH2DVt1z9sVzyznHAp2Nx9-yoGMCgRFP7t=2k5w@mail.gmail.com обсуждение исходный текст |
| Ответ на | [HACKERS] Re: issue: record or row variable cannot be part of multiple-itemINTO list (Anthony Bykov <a.bykov@postgrespro.ru>) |
| Ответы |
[HACKERS] Re: issue: record or row variable cannot be part of multiple-itemINTO list
Re: [HACKERS] Re: issue: record or row variable cannot be part of multiple-item INTO list |
| Список | pgsql-hackers |
Hi
2017-09-14 12:33 GMT+02:00 Anthony Bykov <a.bykov@postgrespro.ru>:
The following review has been posted through the commitfest application:
make installcheck-world: tested, passed
Implements feature: tested, passed
Spec compliant: not tested
Documentation: tested, failed
Hello,
As far as I understand, this patch adds functionality (correct me if I'm wrong) for users. Shouldn't there be any changes in doc/src/sgml/ with the description of new functionality?
It removes undocumented limit. I recheck plpgsql documentation and there are not any rows about prohibited combinations of data types.
There is line:
where command-string is an expression yielding a string (of type text) containing the command to be executed. The optional target is a record variable, a row variable, or a comma-separated list of simple variables and record/row fields, into which the results of the command will be stored. The optional USING expressions supply values to be inserted into the command.
what is correct if I understand well with this patch.
Regards
Pavel
Regards
Anthony
The new status of this patch is: Waiting on Author--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
В списке pgsql-hackers по дате отправления: