> But it can have a different reason. In T-SQL (Microsoft or Sybase) or MySQL > a unbound query is used to direct transfer data to client side.
Are you planning to implement that in PL/pgSQL?
yes. I would to see a stored procedures with this functionality in pg
Currently, PL/pgSQL requires RETURN ____ in order to return a query result to the caller. Is there some reason we'd change that?
it is different functionality.
If you're implementing TSQL-for-PostgreSQL, of course you might want to have different behavior with SELECT. However, TSQL is not PL/pgSQL.
I don't would to implement T-SQL. Same functionality has a PSM in MySQL. And in this moment, there is not any blocker why this should not be in Postgres.
