From: Robert Treat <xzilla@users.sourceforge.net>
To: Bruce Momjian <pgman@candle.pha.pa.us>
Subject: Re: TODO item for plpgsql Was Re: obtuse plpgsql function needs
Date: Wed, 23 Jul 2003 22:00:03 -0400
User-Agent: KMail/1.5
Cc: pgsql-sql@postgresql.org
References: <200307232306.h6NN66P01421@candle.pha.pa.us>
In-Reply-To: <200307232306.h6NN66P01421@candle.pha.pa.us>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200307232200.03736.xzilla@users.sourceforge.net>

On Wednesday 23 July 2003 19:06, Bruce Momjian wrote:
> Robert Treat wrote:
> > On Wed, 2003-07-23 at 15:38, greg@turnstep.com wrote:
> > >   FOR myrec IN EXECUTE myinfo LOOP
> > >     biglist := myrec.info;
> > >   END LOOP;
> >
> > One other thing, I hate when I have to do things like the above, can we
> > get a TODO like:
> >
> > allow 'EXECUTE var INTO record' in plpgsql
>
> So the TODO would be?
>
> 	Allow PL/pgSQL EXECUTE to return a single record outside a loop

that's what I wrote, but not what I meant :-)  I do like the sound of it 
though, but really what I meant to say was:
EXECUTE var1 INTO var2
but this assumes a number of things, namely that executing var1 will return 
only one field, and one row.  I guess that would be:
Allow PL/pgSQL EXECUTE to return a single variable outside a loop

Robert Treat
-- 
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL