----- Original Message -----
From: Ashley Cambrell <ash(at)freaky-namuh(dot)com>
Sent: Monday, October 29, 2001 1:35 AM
> I was just mulling over how hard it would to implement Java stored
> procedures ...
This is an interesting proposal. I was thiniking of it also
some time ago when someone inquired whether PG has PL/Java or not...
> (mulling being the operative word) and was thinking how to
> best implement postgresql <-> java communications. (ie shared memory
> via JNI?) I have read the past posts regarding possible PL/Java
> implementations and it's basically stopped at "How to implement
> Postrgesql <-> Java data passing?".
Maybe the same or a similar way as JDBC folks address it?
> I'm not sure if I'd have time to (nor the skill to) actually implement
> anything, but ...
Same here, but besides having skilled people working on it one has
to initiate the idea first, that's what you did :) and it might
turn out to something more tangeable after fair amount of discussion.
> Instead of using SPI to execute sql, the class would use jdbc to connect
> to the server. The PLJavaLoader class could cache JDBC connections to
> reduce the connection overhead (?).
I'm thinking not to use the JDBC directly, not only to reduce the
connection overhead but also calls to JDBC layer itself. Instead,
one can possibly reuse some of the JDBC code, me thinks.
Just a couple of quick thoughts...
In response to
pgsql-hackers by date
|Next:||From: Robert Dyas||Date: 2001-10-29 20:31:09|
|Subject: Re: consistent naming of components |
|Previous:||From: David Ford||Date: 2001-10-29 20:01:34|
|Subject: Re: [patch] helps fe-connect.c handle -EINTR more gracefully|