X-Original-To: pgsql-sql@postgresql.org
Received: from fzkmail2.fzk.de (fzkmail2.fzk.de [141.52.27.52])
	by postgresql.org (Postfix) with SMTP id DA16A476307
	for <pgsql-sql@postgresql.org>; Wed,  5 Mar 2003 09:10:26 -0500 (EST)
Received: FROM resy5.fzk.de BY fzkmail2.fzk.de ;
 Wed Mar 05 15:10:29 2003 +0100
Received: œby rodos.fzk.de with ESMTP (8.8.6 (PHNE_17135)/8.7.1) id PAA19704; Wed, 5 Mar 2003 15:10:28 +0100 (MET)
Message-ID: <3E660554.23D826D@rodos.fzk.de>
Date: Wed, 05 Mar 2003 15:10:28 +0100
From: Christoph Haller <ch@rodos.fzk.de>
X-Mailer: Mozilla 4.77 [en] (X11; U; HP-UX B.10.20 9000/780)
X-Accept-Language: en
MIME-Version: 1.0
To: pgsql-sql@postgresql.org
Cc: gsstark@mit.edu
Subject: Re: SETOF
Content-Type: text/plain; charset=iso-8859-2
Content-Transfer-Encoding: 7bit
X-Archive-Number: 200303/153
X-Sequence-Number: 12193

>
> That document describes using the function in the from list of the
select.
> That's equivalent to converting the query to a join, which isn't
always
> possible or convenient. I was talking about using a subquery or
function in
> the output column list to produce multiple output columns.
>
I see your point. But, why wouldn't this work in the output column list
too?
The new return form "return next" looks like it could be done.
I'm still hanging around on 7.2, so I can't figure out if it's working
now.

Regards, Christoph