[ http://issues.apache.org/jira/browse/DBCP-179?page=all ]
Phil Steitz updated DBCP-179: ----------------------------- Bugzilla Id: (was: 25696) Fix Version: 1.3 This, and DBCP-175, which it is now almost a dup of, will require API change and should be handled in 1.3 > [dbcp] initializationStatement and destructionStatement in > PoolableConnectionFactory > ------------------------------------------------------------------------------------ > > Key: DBCP-179 > URL: http://issues.apache.org/jira/browse/DBCP-179 > Project: Commons Dbcp > Type: Improvement > Versions: 1.1 Final > 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. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]