Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f18F4px88309; Thu, 8 Feb 2001 10:04:51 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.1/8.11.1) with ESMTP id f18F3t911902; Thu, 8 Feb 2001 10:03:55 -0500 (EST) To: Jan Wieck cc: pgsql-hackers@postgresql.org, pgsql-sql@postgresql.org Subject: Re: [SQL] Re: PL/pgsql EXECUTE 'SELECT INTO ...' In-reply-to: <200102081329.IAA03675@jupiter.greatbridge.com> References: <200102081329.IAA03675@jupiter.greatbridge.com> Comments: In-reply-to Jan Wieck message dated "Thu, 08 Feb 2001 08:29:49 -0500" Date: Thu, 08 Feb 2001 10:03:55 -0500 Message-ID: <11899.981644635@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200102/273 X-Sequence-Number: 4404 Jan Wieck 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 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