aspose file tools*
The moose likes JDBC and the fly likes DriverManager iterating through driver lists, will it create an overhead ? Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Spring in Action this week in the Spring forum!
JavaRanch » Java Forums » Databases » JDBC
Bookmark "DriverManager iterating through driver lists, will it create an overhead ? " Watch "DriverManager iterating through driver lists, will it create an overhead ? " New topic
Author

DriverManager iterating through driver lists, will it create an overhead ?

Shekhar Pareek
Greenhorn

Joined: Aug 28, 2006
Posts: 5
Folks, i read this on a website:

"You need a database connection to manipulate the database. In order to create the connection to the database, the DriverManager class has to know which database driver you want to use.
It does that by iterating over the array (internally a Vector) of drivers that have registered with it and calls the acceptsURL(url) method on each driver in the array, effectively asking the driver to tell it whether or not it can handle the JDBC URL. "

So does it mean whenever we try to create a db connection, the driver manager would iterate through the entire list of drivers which have registered ??
In case the number of drivers registered are substantial, won't this create an overhead ?


Java Ruleth !
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: DriverManager iterating through driver lists, will it create an overhead ?