From: | "jack" <datactrl(at)tpg(dot)com(dot)au> |
---|---|
To: | <pgsql-sql(at)postgresql(dot)org> |
Subject: | Re: About EXECUTE in pl/pgsql |
Date: | 2002-03-25 10:36:15 |
Message-ID: | 010101c1d3e8$e4bb0620$1400a8c0@jac |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
Thank you Tom
----- Original Message -----
From: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "jack" <datactrl(at)tpg(dot)com(dot)au>
Cc: <pgsql-sql(at)postgresql(dot)org>
Sent: Monday, March 25, 2002 5:45 PM
Subject: Re: [SQL] About EXECUTE in pl/pgsql
> "jack" <datactrl(at)tpg(dot)com(dot)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(at)postgresql(dot)org)
>
From | Date | Subject | |
---|---|---|---|
Next Message | Ivan Babikov | 2002-03-25 11:12:16 | Recursive functions aren't possible, are they? |
Previous Message | jack | 2002-03-25 10:33:29 | call the same pl/pgsql procedure twice in the same connection session |