Re: PGConnection vs. Connection

From: Oliver Jowett <oliver(at)opencloud(dot)com>
To: Markus Schaber <schabios(at)logi-track(dot)com>
Cc: "pgsql-jdbc(at)postgresql(dot)org" <pgsql-jdbc(at)postgresql(dot)org>, PostGIS Development Discussion <postgis-devel(at)postgis(dot)refractions(dot)net>, alex bodnaru <alexbodn(at)012(dot)net(dot)il>
Subject: Re: PGConnection vs. Connection
Date: 2005-02-11 20:23:32
Message-ID: 420D1444.3060806@opencloud.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

Markus Schaber wrote:

> the addDataType() methods are carried by the
> org.postgresql.Connection class instead of the
> org.postgresql.PGConnection interface in 7.3 and up.

That's unfortunate :(

> - Prodiding a patch that is to be applied manually (rsp. by the debian
> package build process) when building for 7.2. (this is our "current
> practice").

That seems the simplest approach. Both the 7.2 driver and server are
truely ancient now -- I think having to manually apply a patch if you
want to run against them isn't unreasonable.

> - Using reflection. This could allow us per run-time distinction to use
> o.p.PGConnection.addDataType(Class) when running against pgjdbc 8.0,
> o.p.PGConnection.addDataType(String) against 7.3/7.4, and
> o.p.Connection.addDataType(String) against 7.2. This way we could ship
> a single postgis.jar that runs against all pgjdbc versions.

That seems the most flexible approach, but reflection can be a pain to
deal with. For the packaging case, if you are going to build "PostGIS
for 7.2" and "PostGIS for 8.0" as separate packages then there doesn't
seem like much advantage to having a single PostGIS build/jar anyway.

-O

In response to

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Markus Schaber 2005-02-11 20:51:29 Re: PGConnection vs. Connection
Previous Message Markus Schaber 2005-02-11 15:46:46 PGConnection vs. Connection