From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Jan Wieck <janwieck(at)Yahoo(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org, pgsql-sql(at)postgresql(dot)org |
Subject: | Re: [SQL] Re: PL/pgsql EXECUTE 'SELECT INTO ...' |
Date: | 2001-02-08 15:03:55 |
Message-ID: | 11899.981644635@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-sql |
Jan Wieck <janwieck(at)Yahoo(dot)com> writes:
>> I am inclined to keep our options open by forbidding EXECUTE 'SELECT
>> INTO ...' for now. That's more than a tad annoying, because that leaves
>> no useful way to do a dynamically-built SELECT, but if we don't forbid
>> it I think we'll regret it later.
> You can do something like
> FOR record_var IN EXECUTE <string-expr> LOOP
> ...
> END LOOP;
Okay, that solves the concern I had about not being able to get the
result of an EXECUTEd select at all. I'll go ahead and forbid
EXECUTE 'SELECT INTO' for the time being, and we can talk about
improving plpgsql later.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-02-08 15:10:39 | Re: Re: [SQL] PL/PGSQL function with parameters |
Previous Message | Brent Verner | 2001-02-08 14:58:44 | Re: preproc.y error |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-02-08 15:10:39 | Re: Re: [SQL] PL/PGSQL function with parameters |
Previous Message | omid omoomi | 2001-02-08 13:42:50 | Re: Aggregates and joined tables... |