| From: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: ALTER OBJECT any_name SET SCHEMA name |
| Date: | 2010-10-31 18:19:08 |
| Message-ID: | m2wroycjj7.fsf@2ndQuadrant.fr |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> writes:
>> In particular, embedded and/or dynamic calls in PLs will get hairy if
>> not turing complete and outright impossible to solve.
>
> Sorry, I don't follow. Got an example?
Well, who's to say the following hypothetical plpgsql example should be
forgiven only in an exception's script?
v_sql := 'SELECT * FROM ' || p_fun || '()';
FOR rec in EXECUTE v_sql
LOOP
…
END LOOP;
Regards,
--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2010-10-31 18:30:33 | Re: type info refactoring |
| Previous Message | Andrew Dunstan | 2010-10-31 18:00:41 | Re: why does plperl cache functions using just a bool for is_trigger |