Re: JDBC changes for 7.2... some questions...
От | Ned Wolpert |
---|---|
Тема | Re: JDBC changes for 7.2... some questions... |
Дата | |
Msg-id | XFMail.20010824152343.ned.wolpert@knowledgenet.com обсуждение исходный текст |
Ответ на | JDBC changes for 7.2... some questions... (Ned Wolpert <ned.wolpert@knowledgenet.com>) |
Список | pgsql-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.wolpert@knowledgenet.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-----
В списке pgsql-jdbc по дате отправления: