| From: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Merlin Moncure <mmoncure(at)gmail(dot)com>, Greg <grigorey(at)yahoo(dot)co(dot)uk>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Composite Types and Function Parameters |
| Date: | 2010-10-26 01:02:04 |
| Message-ID: | 25BF3AB9-BDA2-4F26-8967-174CFB9FF43F@kineticode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Oct 25, 2010, at 4:12 PM, Tom Lane wrote:
> However, that objection doesn't hold for plperl or pltcl (and likely
> not plpython, though I don't know that language enough to be sure).
> So it would be a reasonable feature request to teach those PLs to
> accept "record" parameters. I think the fact that they don't stems
> mostly from nobody having revisited their design since the
> infrastructure that supports record_out was created.
+1 # Would love to see that.
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2010-10-26 01:07:36 | Re: Range Types, discrete and/or continuous |
| Previous Message | Greg Stark | 2010-10-26 00:57:54 | Re: foreign keys for array/period contains relationships |