Re: ROWS FROM(): A Foolish (In)Consistency?
От | Robert Haas |
---|---|
Тема | Re: ROWS FROM(): A Foolish (In)Consistency? |
Дата | |
Msg-id | CA+TgmoYcr=MBCJwcxdfx4f_NJf_x=2b-ff-Bs10gwNBKkN6tJA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: ROWS FROM(): A Foolish (In)Consistency? (Jim Nasby <Jim.Nasby@BlueTreble.com>) |
Ответы |
Re: ROWS FROM(): A Foolish (In)Consistency?
|
Список | pgsql-hackers |
On Mon, Oct 19, 2015 at 8:02 PM, Jim Nasby <Jim.Nasby@bluetreble.com> wrote: > On 10/19/15 1:07 PM, David Fetter wrote: >> >> What I'd like to do is lift the restriction on ROWS FROM(), which >> currently requires that the stuff inside the parentheses set-returning >> functions, so constructs something like the following would actually work: >> >> SELECT * >> FROM >> ROWS FROM ( >> (VALUES (...), ..., (...)), >> (SELECT ... ), >> (INSERT ... RETURNING ... ), >> my_srf() >> ) >> AS t(...) >> >> would actually work. > > > There's been a few places where I would have found that handy. Why not just use a subquery with UNION ALL? -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: