From: | Markus Schaber <schabios(at)logi-track(dot)com> |
---|---|
To: | pgsql-jdbc(at)postgresql(dot)org |
Cc: | Edoardo Ceccarelli <eddy(at)axa(dot)it> |
Subject: | Re: blob without largeobject api |
Date: | 2004-06-21 15:44:26 |
Message-ID: | 20040621174426.097e55ad@kingfisher.intern.logi-track.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Hi, Oliver,
On Wed, 07 Apr 2004 00:24:35 +1200
Oliver Jowett <oliver(at)opencloud(dot)com> wrote:
> Edoardo Ceccarelli wrote:
> > Tried with a driver downloaded from http://jdbc.postgresql.org/
> >
> > pg74.213.jdbc3.jar
> >
> > the result is always the same:
> > java.lang.ClassCastException: com.caucho.sql.UserConnection
> > on row:
> > LargeObjectManager lom =
> > ((org.postgresql.PGConnection)db).getLargeObjectAPI();
>
> Ok, this means your pooling implementation is not using the postgresql
> driver's PooledConnection to generate the proxy connections to hand
> out, but is implementing them itself (using instances of
> com.caucho.sql.UserConnection, it appears). So you won't be able to
> get at postgresql-specific interfaces with that pooling
> implementation, regardless of what the driver does.
Maybe his pooling implementation provides a method to get to the
underlying "real" connection.
In one of our projects, we had to use this Trick to add the PostGIS
Wrapper Classes to the JDBC Driver.
HTH,
Markus
--
markus schaber | dipl. informatiker
logi-track ag | rennweg 14-16 | ch 8001 zürich
phone +41-43-888 62 52 | fax +41-43-888 62 53
mailto:schabios(at)logi-track(dot)com | www.logi-track.com
From | Date | Subject | |
---|---|---|---|
Next Message | Markus Schaber | 2004-06-21 16:20:05 | Re: what is lslowing me down? JDBC or Postgresql itself? |
Previous Message | Laurent Sylvain | 2004-06-21 13:00:09 | Bug (and fix): leaks of TCP connections when connected to a <7.4 server |