| From: | Rene Pijlman <rpijlman(at)wanadoo(dot)nl> |
|---|---|
| To: | Ned Wolpert <ned(dot)wolpert(at)knowledgenet(dot)com> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, "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:02:02 |
| Message-ID: | n9jdotghls8imt867bivv2nntfqtma5s7b@4ax.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-jdbc |
On Fri, 24 Aug 2001 12:53:55 -0700 (MST), you wrote:
>It's not accessiable since its not in the JDBC spec. Specifically, when you
>use PoolMan (www.codestudio.com) as the pooling manager, PoolMan has its own
>JDBC classes that wraps any JDBC compliant driver.
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ian Lance Taylor | 2001-08-24 22:11:48 | Re: A couple items on TODO |
| Previous Message | Ian Lance Taylor | 2001-08-24 21:38:53 | Re: User locks code |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ned Wolpert | 2001-08-24 22:23:43 | Re: JDBC changes for 7.2... some questions... |
| Previous Message | Bruce Momjian | 2001-08-24 21:31:33 | Re: Bug #428: Another security issue with the JDBC driver. |