This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I am writing a 'service file'. In this i am using more number of 'sql connections'. As of now i have declared Connection, PrepareStatement, ResultSet in Class level. So i am using these in my code again and again. ie. Every time i am creating new connection and closing it again.
Yesterday my friend said me to use a single connection through out the code. Like with out closing the connection.
Please help me.. Which better way(When i am using more SQL statements)
I would use a connection pool. Even if it only has one connection, this lets the pool handle it for you. Keeping one connection open too long can give you a timeout error. Whereas getting a connection from the pool is much cheaper than getting a new one each time.