Re: TODO item for plpgsql Was Re: obtuse plpgsql function needs

From: Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: pgsql-sql(at)postgresql(dot)org
Subject: Re: TODO item for plpgsql Was Re: obtuse plpgsql function needs
Date: 2003-07-24 02:00:03
Message-ID: 200307232200.03736.xzilla@users.sourceforge.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

On Wednesday 23 July 2003 19:06, Bruce Momjian wrote:
> Robert Treat wrote:
> > On Wed, 2003-07-23 at 15:38, greg(at)turnstep(dot)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

In response to

Responses

Browse pgsql-sql by date

  From Date Subject
Next Message Tom Lane 2003-07-24 05:07:18 Re: obtuse plpgsql function needs
Previous Message Jamie Lawrence 2003-07-23 23:31:05 More plsql questions: updates on views