Skip site navigation (1) Skip section navigation (2)

Re: Pl/Java 1.0.0.b now avaiable on Linux 386 and Cygwin

From: "Thomas Hallgren" <thhal(at)mailblocks(dot)com>
To: <pg(at)fastcrypt(dot)com>
Cc: <pgsql-jdbc(at)postgresql(dot)org>
Subject: Re: Pl/Java 1.0.0.b now avaiable on Linux 386 and Cygwin
Date: 2004-02-10 14:05:16
Message-ID: 004901c3efde$ed5673f0$ (view raw, whole thread or download thread mbox)
Lists: pgsql-jdbc
> Thomas,
> Do you have a feature list, and or a roadmap where you want to take
> this?

I'm planning on writing a roadmap. At present, I'm logging tasks that I feel
should be implemented in the task list of the project. If you go here: and search for
"Not closed", you get a fairly good idea of the near future.

Long term, it depends a bit on what kind of reception the project will have.
My objective is to eventually have it accepted and included in PostgreSQL.
Don't know the best route to get there though. Any advice is appreciated :-)

The project also have a "Feature requests" mechanism where I encourage
anyone with interest to add things they think would benefit the project.

> Have you any ideas for supporting jdbc calls from within the java
> function?
I do indeed. Most of the things you do with Pl/Java is done using JDBC calls
from within java. The JDBC driver maps the calls to SPI. As I browse the
user doc's I realize I actually missed the section regarding this support
(will add promptly). Some of the samples in the download (
shows how it's done though.

In essence, there's a default connection available using:

    Connection conn =

From there on, you can prepare and execute statements, and use ResultSet's.
Just like with any JDBC driver. The only thing not implemented yet is

In fact, much of the management routines (install_jar, replace_jar, etc.) is
written in Java using the JDBC interfaces.


Thomas Hallgren

In response to

pgsql-jdbc by date

Next:From: shawnDate: 2004-02-10 14:10:32
Subject: unsubscribe
Previous:From: Dave CramerDate: 2004-02-10 13:59:12
Subject: Re: closing statements when connection is closed

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group