Pavel,
> 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?
Currently, PL/pgSQL requires RETURN ____ in order to return a query
result to the caller. Is there some reason we'd change that?
If you're implementing TSQL-for-PostgreSQL, of course you might want to
have different behavior with SELECT. However, TSQL is not PL/pgSQL.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
