| From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Karen Hill <karen_hill22(at)yahoo(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: US Telephone Number Type |
| Date: | 2006-07-11 14:17:12 |
| Message-ID: | 20060711141712.GA6500@svana.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Jul 11, 2006 at 01:27:49AM -0400, Alvaro Herrera wrote:
> But I think the main problem may be getting our calling conventions
> right. I mean, how would you do a PG_GETARG_BOOL() or stuff like that?
> Maybe if we offered PG_GETARG_DATUM and PG_RETURN_DATUM equivalents in
> PL/Perl we could offer I/O functions there.
Not sure what you're getting at, type input/output functions are no
different than other functions.
Historically I beleive the issue was that languages couldn't handle the
"cstring" type because it was special. As of recent releases that's not
a problem anymore (though pl/pgsql still doesn't understand it for
example).
Another issue was that there was a special hack to create type
input/output functions because of the chicken/egg issue of type
creation. With explicit shell types this is fixed also (in -HEAD).
AIUI, pl/java can do it. For the others I just don't think people have
really tried...
Have a nice day,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-07-11 14:17:40 | Re: customizing pg_dump together with copy.c's DoCopy function |
| Previous Message | Robert Fitzpatrick | 2006-07-11 13:43:51 | Error code 1063 |