Re: [HACKERS] Re: issue: record or row variable cannot be part ofmultiple-item INTO list
| От | David G. Johnston |
|---|---|
| Тема | Re: [HACKERS] Re: issue: record or row variable cannot be part ofmultiple-item INTO list |
| Дата | |
| Msg-id | CAKFQuwa++t=SPyXfQHX4OjGMzzetkkitDuJsQ2dCaHVDYvhOOg@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: [HACKERS] Re: issue: record or row variable cannot be part of multiple-item INTO list (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: [HACKERS] Re: issue: record or row variable cannot be part of multiple-item INTO list
Re: [HACKERS] Re: issue: record or row variable cannot be part of multiple-item INTO list |
| Список | pgsql-hackers |
Aside from being inconsistent, it doesn't cover all
the cases --- what if you have just one query output column, that is
composite, and you'd like it to go into a composite variable? That
doesn't work today, and this patch doesn't fix it, but it does create
enough confusion that we never would be able to fix it.
Actually, this does work, just not the way one would immediately expect.
ct1: (text, text)
DO $$
SELECT ('1', '2')::ct1 INTO c1;
RAISE NOTICE '%', c1;
END;
$$;
Notice: ("(1,2)",)
And so, yes, my thinking has a backward compatibility problem. But one that isn't fixable when constrained by backward compatibility - whether this patch goes in or not.
David J.
В списке pgsql-hackers по дате отправления: