Name: krT82822 Date: 02/27/2000


(please see Comments section)

java version "1.3beta"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3beta-O)
Java(TM) HotSpot Client VM (build 1.3beta-O, mixed mode)

Working with Oracle 8.1.6 implementation of javax.sql, it seems a
PooledConnection has no way to preserve its PreparedStatements with its physical
connection. They are lost when the logical connection is closed, thus erasing
the performance benefit of query plans. Looking at the javax.sql API, it seems
to be a problem that is designed into the API.

--------------------------

1/25/2000 further notes from user:

Actually, I have not used the javax.sql directly. Just the Oracle 8.1.6
implementation of javax.sql. I am not sure what version of javax.sql
Oracle is using for this. If you need further details, please ask.
However, I do not think my inquiry depends on any testing.
I see it as question of how the API is defined and how to use it.
(Review ID: 100318)
======================================================================