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

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

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. Since this method is
specific to PostgreSQL, it's not in the standard JDBC classes. Most JDBC
poolers wrap classes similarly. (Well, except oracle's pool manager. They
provide their own pooling manager.)

In any case, I think this functionality is useful beyond just JDBC.

On 24-Aug-2001 Peter Eisentraut wrote:
> Ned Wolpert writes:
>
>> Now, I understand that in the Statement class, we have getInsertedOID() in
>> the
>> table. However, the problem we run into is that this isn't accessiable if
>> we
>> use something like poolman to provide database pooling of connections. (You
>> get the poolMan Statement object which is wraps the Statement classes of the
>> driver.)
>
> I think no one has asked yet *why* it isn't "accessible".
>
> Maybe the getInsertedOID function needs to be moved to some other class?
>
> --
> Peter Eisentraut peter_e(at)gmx(dot)net http://funkturm.homeip.net/~peter

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

iD8DBQE7hrDTiysnOdCML0URAj93AJ9fPjtXEuVj6Wvc6bbOp/eEV6EdtACdEqe+
/MCOd239rhEXfb4j1yajuoQ=
=nem4
-----END PGP SIGNATURE-----