Skip site navigation (1) Skip section navigation (2)

Re: returning multiple result sets from a stored procedure

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Darren Duncan" <darren(at)darrenduncan(dot)net>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: returning multiple result sets from a stored procedure
Date: 2010-09-09 21:09:42
Message-ID: 4C8906C602000025000354A7@gw.wicourts.gov (view raw or flat)
Thread:
Lists: pgsql-hackers
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
 
> I don't understand the point of a RETURN value when there can be
> no caller to return a value to.
 
The version of the draft standard I last saw allowed something like:
 
SET x = CALL sp(param_a, param_b);
 
I seem to remember Sybase supported a return value as well as OUT
parameters, too; I think there it was limited to integer values and
was conventionally used to indicate overall success or failure of
the procedure.
 
-Kevin

In response to

pgsql-hackers by date

Next:From: Darren DuncanDate: 2010-09-09 21:12:24
Subject: Re: returning multiple result sets from a stored procedure
Previous:From: Tom LaneDate: 2010-09-09 21:07:41
Subject: Re: returning multiple result sets from a stored procedure

Privacy Policy | About PostgreSQL
Copyright © 1996-2013 The PostgreSQL Global Development Group