Base JDBC datastore factory should allow minimal control over the connection
pool
---------------------------------------------------------------------------------
Key: GEOT-1963
URL: http://jira.codehaus.org/browse/GEOT-1963
Project: GeoTools
Issue Type: Improvement
Affects Versions: 2.5-RC0
Reporter: Andrea Aime
Fix For: 2.5.0, 2.6-M0
In particular, it should provide minimal support for setting the pool size, and
for allowing the connection check before the the connection itself is used.
Prepared statement pool size would be most convinienent as well.
I understand with H2 embedded connection pooling is not necessary, but that's
the exception, not the rule.
Most production enviroments I dealt with had pretty strict connection pool
rules, such as, "you _have_ to use one, max size is 7, never keep more than 2
around if not needed thought" or some such. Prepared statemetns connection pool
size is crucial too, Oracle for example need special settings on the dbms
server side to allow the pool (both connection and ps wise) to grow beyond a
certain size.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
