| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| 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 14:07:09 |
| Message-ID: | 4136.1253110029@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> 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.
IIRC the original complaint was from someone trying to migrate code
from T/SQL or some other not-quite-PLSQL language. Like you, I'm on
the fence about whether to accept this patch, but it does have some
in-migration rationale.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2009-09-16 14:17:20 | Re: PATCH: make plpgsql IN args mutable (v1) [REVIEW] |
| Previous Message | Alvaro Herrera | 2009-09-16 13:59:46 | Re: PATCH: make plpgsql IN args mutable (v1) [REVIEW] |