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 Thu, 27 Mar 2003 18:57:46 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-27 18:57 -------
It's not clear to me why we need the maxOpenStatements property.  The docs say 
it's to prevent resource leaks but can you be more specific?  


An alternative implementation of the statement pooling could be done by the 
Connection rather than the DataSource.  Because a different statement pool is 
created for each Connection, it might make sense to put this behavior in the 
Connection class.

---------------------------------------------------------------------
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