From: jack <datactrl@tpg.com.au>
To: pgsql-sql@postgresql.org
Subject: Re: About EXECUTE in pl/pgsql
Date: Mon, 25 Mar 2002 20:36:15 +1000
Message-ID: <010101c1d3e8$e4bb0620$1400a8c0@jac> (raw)
References: <003401c1d3af$17bf8710$1400a8c0@jac>
<17454.1017042309@sss.pgh.pa.us>
Thank you Tom
----- Original Message -----
From: "Tom Lane" <tgl@sss.pgh.pa.us>
To: "jack" <datactrl@tpg.com.au>
Cc: <pgsql-sql@postgresql.org>
Sent: Monday, March 25, 2002 5:45 PM
Subject: Re: [SQL] About EXECUTE in pl/pgsql
> "jack" <datactrl@tpg.com.au> 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)
>
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 using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: datactrl@tpg.com.au
Subject: Re: About EXECUTE in pl/pgsql
In-Reply-To: <010101c1d3e8$e4bb0620$1400a8c0@jac>
* 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