db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Suavi Ali Demir <dem...@yahoo.com>
Subject Re: Unit tests with Derby DB
Date Wed, 14 Sep 2005 17:38:03 GMT
Thanks for the clarification. Some applications might be actually registering the driver themselves.
What are the problems that this might cause (if the app calls DriverManager.registerDriver()
explicitly)?
Regards,
Suavi


Daniel John Debrunner <djd@debrunners.com> wrote:
Suavi Ali Demir wrote:

> After a shutdown=true, you should be able to connect to the same
> database again after doing a DriverManager.registerDriver(
> Class.forName(driverName).newInstance() )

No, that's not the correct way to start Derby or any other JDBC driver.
JDBC drivers are required to register themselves, applications should
not be registering drivers.
Simply loading the driver and creating an instance of it will start
Derby again.

Class.forName(driverName).newInstance();

Dan.



Mime
View raw message