| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Abhijit Menon-Sen <ams(at)toroid(dot)org>, pgsql-hackers(at)postgresql(dot)org, Steve Prentice <prentice(at)cisco(dot)com> |
| Subject: | Re: PATCH: make plpgsql IN args mutable (v1) [REVIEW] |
| Date: | 2009-09-16 13:59:46 |
| Message-ID: | 20090916135946.GF13076@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Dunstan wrote:
> It probably won't cause any problem with code being migrated from
> PLSQL, but it will affect code going the other way. The question is:
> do we care about that? I'm prepared to be persuaded that we
> shouldn't care, but I'm not quite there yet.
Anybody trying to port code from PL/pgSQL to PL/SQL is going to be a lot
more inconvenienced by the OUT parameter stuff.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-09-16 14:07:09 | Re: PATCH: make plpgsql IN args mutable (v1) [REVIEW] |
| Previous Message | Alvaro Herrera | 2009-09-16 13:57:50 | Re: errcontext support in PL/Perl |