[DBCP-179] [dbcp] initializationStatement and destructionStatement in PoolableConnectionFactory

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Won't Fix
• Affects Version/s: 1.1
• Fix Version/s: 1.3

Environment

Operating System: All
Platform: All

• Bugzilla Id: 25696
• Assignee: Unassigned
• Reporter: Dirk Verbeeck
• Created: 22/Dec/03 21:32
• Updated: 15/Feb/10 04:12
• Resolved: 12/Sep/09 21:56

Description

proposal & patch from Brent Verner (slightly edited)
-----------------------------------------------------
I've often had the need to perform some setup of a connection
before it can be used, such as:

ALTER SESSION SET current_schema = workable_schema;

As such, I've had a hacked version of dbcp around for a while
that adds an initializationStatement and destructionStatement.
Both are fed thru the Statement.execute(String) method, and
nothing is done with any (possible) ResultSet from the query.
These statements are executed in the makeObject() and destroyObject() methods of
PoolableConnectionFactory.

Issue Links

• is part of: DBCP-175 [dbcp] I'd like to run init SQL after JDBC Connection creation in Tomcat DBCP