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

Re: JDBC changes for 7.2... some questions...

From: Ned Wolpert <ned(dot)wolpert(at)knowledgenet(dot)com>
To: Rene Pijlman <rpijlman(at)wanadoo(dot)nl>
Cc: "pgsql-jdbc(at)postgresql(dot)org" <pgsql-jdbc(at)postgresql(dot)org>
Subject: Re: JDBC changes for 7.2... some questions...
Date: 2001-08-24 22:23:43
Message-ID: XFMail.20010824152343.ned.wolpert@knowledgenet.com (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-jdbc
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Yes.  Every class is wrapped; that is how most connection pooling managers in
Java tend to work.

Specifically, you load PoolMan directly (via DriverManager) or indirectly
(JNDI) and it reads its configuration properties to figure out what classes to
load.  You only have access to PoolMan's classes, which are a proxy to the
PostgreSQL JDBC classes. (Or which-ever JDBC classes that are in use. PoolMan
works with and JDBC-compliant driver and datasource.)

On 24-Aug-2001 Rene Pijlman wrote:
> Do they also wrap Connection? Since the last oid is associated
> with a client connection to the backend, it might be a solution
> to add a getLastOID() method to Connection.
> 
> Regards,
> Ren Pijlman


Virtually, 
Ned Wolpert <ned(dot)wolpert(at)knowledgenet(dot)com>

D08C2F45:  28E7 56CB 58AC C622 5A51  3C42 8B2B 2739 D08C 2F45 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE7htPviysnOdCML0URApzMAKCAp5PpDRXkQVRgkin46+QvibJFogCdFQsl
sFesIHynhct9C+CEQSK6WZs=
=wnEQ
-----END PGP SIGNATURE-----

In response to

pgsql-hackers by date

Next:From: Ian Lance TaylorDate: 2001-08-24 22:26:12
Subject: Re: List response time...
Previous:From: Ian Lance TaylorDate: 2001-08-24 22:22:47
Subject: Re: List response time...

pgsql-jdbc by date

Next:From: Dave HarknessDate: 2001-08-24 23:57:11
Subject: Re: JDBC changes for 7.2... some questions...
Previous:From: Rene PijlmanDate: 2001-08-24 22:02:02
Subject: Re: JDBC changes for 7.2... some questions...

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