commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 18012] - BasicDataSource doesn't include PreparedStmt Pooling
Date Fri, 28 Mar 2003 22:00:14 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18012>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18012

BasicDataSource doesn't include PreparedStmt Pooling





------- Additional Comments From dgraham@apache.org  2003-03-28 22:00 -------
I still don't see the need for a maxOpenStatements parameter.  If a thread calls 
conn.prepareStatement("some query") and that PS is already checked out of the 
pool, then you can throw an exception.


JDBC implementations requiring you to close the ResultSet are in violation of 
the spec so that's not our problem.  It would be nice if the spec said that PS 
should be closed when the Connection.close() method is called but I can't find 
that in the javadocs.  So, clients still have to close each PS manually to 
return them to the pool.

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message