Re: PL/pgSQL stored procedure returning multiple result sets (SELECTs)?

On Tue, 14 Oct 2008 16:51:29 -0400
"Merlin Moncure" <mmoncure(at)gmail(dot)com> wrote:

> Functions are limited in the sense that it is awkward to return
> multiple sets, but are much more flexible how they can be
> integrated into queries -- you can call a function anywhere a
> scalar or a set is allowed -- in addition to the monolithic
> procedure style.

From a security point of view... stored procedures can't be called
inside another statement making it harder to hide them for sql
injection.

> While the inability to return directly two sets from the same
> function is annoying (I would use arrays today, this was one of
> the reasons why we wrote libpqtypes), you have to understand that
> in virtually all other respects postgresql pl/pgsql is light years
> beyond the lousy psm implementation in mysql. The way we handle

That's one of the reasons that made me chose postgresql in spite of
mysql. PostgreSQL is easier to program and its programming
"infrastructure" is MUCH MUCH more mature.

--
Ivan Sergio Borgonovo
http://www.webthatworks.it