On Wed, May 21, 2008 at 1:28 PM, Hannu Krosing <hannu(at)krosing(dot)net> wrote:
>> In my proposal I don't create any default variables. Result type is
>> only virtual - I don't need write it to system directory. I thing it's
>> better than using some specific predeclared type as RESULTTYPE OR
>> RESULTSET.
>
> How is this different from using OUT params and RETURNS SETOF RECORD ?

*) you reference output variables via rowtype (r.var vs. var)
*) seems cleaner to separate in/out variables so add/drop function are
symmetric.

Also,
What about:

CREATE OR REPLACE FUNCTION foo(m integer)
RETURNS TABLE (a integer, b integer) AS $$
  -- DECLARE r foo; -- make alias of r to foo optional
BEGIN
 FOR i IN 1..m LOOP
     foo.a := i; foo.b := i + 1;
[...]

or
RETURNS TABLE r(a integer, b integer) AS $$

merlin

In response to

• Re: proposal: table functions and plpgsql at 2008-05-21 17:28:12 from Hannu Krosing

Responses

• Re: proposal: table functions and plpgsql at 2008-05-21 18:14:47 from Hannu Krosing
• Re: proposal: table functions and plpgsql at 2008-05-21 21:03:53 from Pavel Stehule

pgsql-hackers by date

Next:	From: Tom Lane	Date: 2008-05-21 18:07:56
	Subject: May Commitfest is done!
Previous:	From: Hannu Krosing	Date: 2008-05-21 17:28:12
	Subject: Re: proposal: table functions and plpgsql