[
https://issues.apache.org/jira/browse/DBCP-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12732914#action_12732914
]
Phil Steitz commented on DBCP-179:
----------------------------------
I am inclined to close this as WONTFIX, given that DBCP-175 has been addressed.
I don't see the "destruction" case as something that the pool itself should
handle.
> [dbcp] initializationStatement and destructionStatement in
> PoolableConnectionFactory
> ------------------------------------------------------------------------------------
>
> Key: DBCP-179
> URL: https://issues.apache.org/jira/browse/DBCP-179
> Project: Commons Dbcp
> Issue Type: Improvement
> Affects Versions: 1.1
> Environment: Operating System: All
> Platform: All
> Reporter: Dirk Verbeeck
> Priority: Minor
> Fix For: 1.3
>
> Attachments: pcf.diff
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
