It actually depends on how you intend to use the connection.
As a simple scenario, let us say you execute some queries (select/update) but only one at a time. Creating connection each time is not the right way and you can use the same connection.
You want to execute many queries simultaneously, then you can still reuse the connection provided you are doing only select queries.
Finally if the requirement is like multiple queries simultaneously, both selects and updates - yes this requires for separate connections. In this situation also you would be better off by using some kind of pooling. [ October 17, 2008: Message edited by: Phani Raju ]
Joined: Jul 18, 2007
I am using the last scenario you mentioned. I'll look at the pooling topic and try to come up with a better logic.
Sounds a good idea; maybe better to have a close() method in your own class so you call close() rather than con.close(); this enables you to put your null checking and exception handling all in one place.
Sounds like a candidate for transfer to JDBC where this sort of topic is usually discussed.
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com