Received: from mail1.tpgi.com.au (mail.tpgi.com.au [203.12.160.57]) by postgresql.org (Postfix) with ESMTP id 14F5C47598F for ; Mon, 25 Mar 2002 05:36:16 -0500 (EST) Received: from jac (bri5-56k-062.tpgi.com.au [203.213.6.62]) by mail1.tpgi.com.au (8.11.6/8.11.6) with SMTP id g2PAaGj16577 for ; Mon, 25 Mar 2002 21:36:17 +1100 Message-ID: <010101c1d3e8$e4bb0620$1400a8c0@jac> From: "jack" To: References: <003401c1d3af$17bf8710$1400a8c0@jac> <17454.1017042309@sss.pgh.pa.us> Subject: Re: About EXECUTE in pl/pgsql Date: Mon, 25 Mar 2002 20:36:15 +1000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Archive-Number: 200203/310 X-Sequence-Number: 7189 Thank you Tom ----- Original Message ----- From: "Tom Lane" To: "jack" Cc: Sent: Monday, March 25, 2002 5:45 PM Subject: Re: [SQL] About EXECUTE in pl/pgsql > "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. > > regards, tom lane > > ---------------------------(end of broadcast)--------------------------- > TIP 2: you can get off all lists at once with the unregister command > (send "unregister YourEmailAddressHere" to majordomo@postgresql.org) >