Postgres Pro
Downloads
Home   >   mailing lists

Re: Using scalar function as set-returning: bug or feature? - Mailing list pgsql-hackers

From Marko Tiikkaja
Subject Re: Using scalar function as set-returning: bug or feature?
Date
Msg-id CAL9smLALdNruR_3_Oqw+DENyadbzVt0i3fVKpxNO=BoZjadJYA@mail.gmail.com
Whole thread Raw
In response to Re: Using scalar function as set-returning: bug or feature?  ("Tels" <nospam-pg-abuse@bloodgate.com>)
List pgsql-hackers
Tree view
On Tue, Feb 13, 2018 at 12:30 PM, Tels <nospam-pg-abuse@bloodgate.com> wrote:
I'm not sure if you mean exactly the scenario as in the attached test
case, but this works in plpgsql, too, and would be a shame to lose.

OTOH, one could also write:

  SELECT INTO ba, bb  a,b FROM foo(1);

and it would still work, or wouldn't it?

Yes.  The code in test.psql shouldn't pass code review.


.m

pgsql-hackers by date:

Previous
From: "Tels"
Date:
Subject: Re: Using scalar function as set-returning: bug or feature?
Next
From: Etsuro Fujita
Date:
Subject: Re: postgres_fdw: perform UPDATE/DELETE .. RETURNING on a join directly