From: "Jim Buttafuoco" <jim@contactbda.com>
To: "Mark R. Dingee" <mark.dingee@cox.net>, pgsql-sql@postgresql.org
Reply-To: jim@contactbda.com
Subject: Re: Multi-column returns from pgsql
Date: Fri, 22 Jul 2005 12:56:15 -0400
Message-Id: <20050722165558.M96628@contactbda.com>
In-Reply-To: <200507221149.21550.mark.dingee@cox.net>
References: <200507221149.21550.mark.dingee@cox.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset=iso-8859-1

Mark,

Instead of  RETURN NEXT rec.txt1; RETURN NEXT rec.txt2; just use RETURN NEXT rec;

then your select statement would be 
select * from my_func() as (txt1 text,txt2 text);

Jim


---------- Original Message -----------
From: "Mark R. Dingee" <mark.dingee@cox.net>
To: pgsql-sql@postgresql.org
Sent: Fri, 22 Jul 2005 11:49:21 -0400
Subject: [SQL] Multi-column returns from pgsql

> Hi Everyone,
> 
> Does anyone know if/how it's possible to return multi-column sets from a pgsql 
> function?  Right now I'm using something like the following as a work around
> 
> CREATE OR REPLACE FUNCTION my_func() returns SETOF TEXT AS '
> DECLARE
>     rec record;
> BEGIN
>     FOR rec IN SELECT txt1, txt2 FROM mytable LOOP
>        RETURN NEXT rec.txt1;
>        RETURN NEXT rec.txt2;
>     END LOOP;
>     RETURN;
> END;' language 'plpgsql';
> 
> which leaves me parsing multiple records to achieve the desired end result.
> 
> Anyone have any thoughts?
> 
> Thanks,
> Mark
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
>        choose an index scan if your joining column's datatypes do not
>        match
------- End of Original Message -------