Received: from store.d.zembu.com (nat.zembu.com [209.128.96.253]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f185Xlx43626 for ; Thu, 8 Feb 2001 00:33:48 -0500 (EST) (envelope-from ncm@zembu.com) Received: by store.d.zembu.com (Postfix, from userid 509) id EB532A782; Wed, 7 Feb 2001 21:33:47 -0800 (PST) Date: Wed, 7 Feb 2001 21:33:47 -0800 To: pgsql-hackers@postgreSQL.org Subject: Re: PL/pgsql EXECUTE 'SELECT INTO ...' Message-ID: <20010207213347.A19999@store.zembu.com> Reply-To: pgsql-hackers@postgreSQL.org References: <10497.981602102@sss.pgh.pa.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <10497.981602102@sss.pgh.pa.us>; from tgl@sss.pgh.pa.us on Wed, Feb 07, 2001 at 10:15:02PM -0500 From: ncm@zembu.com (Nathan Myers) X-Archive-Number: 200102/265 X-Sequence-Number: 4396 On Wed, Feb 07, 2001 at 10:15:02PM -0500, Tom Lane wrote: > I have looked a little bit at what it'd take to make SELECT INTO inside > an EXECUTE work the same as it does in plain plpgsql ... > If we do nothing now, and then implement this feature in 7.2, we will > have a backwards compatibility problem: EXECUTE 'SELECT INTO ...' > will completely change in meaning. > > I am inclined to keep our options open by forbidding EXECUTE 'SELECT > INTO ...' for now. ... if [not] I think we'll regret it later. I agree, disable it. But put a backpatch into contrib along with a reference to this last e-mail. Anybody who cares enough can apply the patch, and will be prepared for the incompatibility. Nathan Myers ncm@zembu.com