Re: Bug 9064 Not Quite Fixed (3.1.10)?
Yeah, I never intended to imply that ParseInfo would be the solution to the problem. I didn't examine the code completely in depth but enough to wonder why a forced string copy was occuring.
I suppose now I'm starting to make a little bit of a fool out of myself. We've written our own pooling and initialization system that loads the statements and things from XML files to dynamically construct SQL (it can change depending on database being connected to). I don't know that much about any "standard" connection pooling, and the one time I tried to figure it out (along with JNDI data sources), I got a bit confused so we still use the old Class.forName and DriverManager method.
Jason Winnebeck
Center for Integrated Manufacturing Studies
Rochester Institute of Technology, Rochester NY
Subject
Written By
Posted
Re: Bug 9064 Not Quite Fixed (3.1.10)?
July 26, 2005 11:25AM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.