From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jan Wieck <janwieck@Yahoo.com>
Cc: pgsql-hackers@postgresql.org
Cc: pgsql-sql@postgresql.org
Subject: Re: [SQL] Re: PL/pgsql EXECUTE 'SELECT INTO ...'
Date: Thu, 08 Feb 2001 10:03:55 -0500
Message-ID: <11899.981644635@sss.pgh.pa.us> (raw)
In-Reply-To: <200102081329.IAA03675@jupiter.greatbridge.com>
References: <200102081329.IAA03675@jupiter.greatbridge.com>
Jan Wieck <janwieck@Yahoo.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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, janwieck@Yahoo.com, pgsql-hackers@postgresql.org
Subject: Re: [SQL] Re: PL/pgsql EXECUTE 'SELECT INTO ...'
In-Reply-To: <11899.981644635@sss.pgh.pa.us>
References: <200102081329.IAA03675@jupiter.greatbridge.com> <11899.981644635@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox