Re: ROWS FROM(): A Foolish (In)Consistency? - Mailing list pgsql-hackers

From Robert Haas
Subject Re: ROWS FROM(): A Foolish (In)Consistency?
Date
Msg-id CA+TgmoYcr=MBCJwcxdfx4f_NJf_x=2b-ff-Bs10gwNBKkN6tJA@mail.gmail.com
Whole thread Raw
In response to Re: ROWS FROM(): A Foolish (In)Consistency?  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
Responses Re: ROWS FROM(): A Foolish (In)Consistency?  (David Fetter <david@fetter.org>)
List 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 by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: Multi-column distinctness.
Next
From: Robert Haas
Date:
Subject: Re: Dangling Client Backend Process