Received: from candle.pha.pa.us (216-55-132-35.dsl.san-diego.abac.net [216.55.132.35]) by postgresql.org (Postfix) with ESMTP id 53072475E59 for ; Mon, 25 Mar 2002 15:58:42 -0500 (EST) Received: (from pgman@localhost) by candle.pha.pa.us (8.11.6/8.10.1) id g2PKwSM15186; Mon, 25 Mar 2002 15:58:28 -0500 (EST) From: Bruce Momjian Message-Id: <200203252058.g2PKwSM15186@candle.pha.pa.us> Subject: Re: About EXECUTE in pl/pgsql In-Reply-To: <17454.1017042309@sss.pgh.pa.us> To: Tom Lane Date: Mon, 25 Mar 2002 15:58:28 -0500 (EST) Cc: jack , pgsql-sql@postgresql.org X-Mailer: ELM [version 2.4ME+ PL97 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Archive-Number: 200203/328 X-Sequence-Number: 7203 Tom Lane wrote: > "jack" writes: > > I do following in pl/pgsql. (st1 has been set to "LIKE 'abc%' ") > > > EXECUTE > > ''CREATE TEMP TABLE comuser AS '' || > > ''SELECT * FROM comt_user1 WHERE username ''||St1|| > > ''ORDER BY username;''; > > > I've got "ERROR: EXECUTE ..SELECT INTO hasn't impletmented", How can?? > > Ooops :-(. That check was intended to prevent SELECT ... INTO table > from being used in EXECUTE, mainly because of the confusion factor > (SELECT INTO in plpgsql doesn't mean what it means in SQL, but the > SQL interpretation is what you'd get from EXECUTE). > > However, the check wasn't intended to trigger on CREATE AS. > > I've stuck a quick fix into the current sources. Should be in 7.2.1. CVS current and 7.2.X CVS HISTORY/release.sgml updated with: Allow CREATE TABLE AS ... SELECT in PL/PgSQL (Tom) -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026