Usually, you will not need to create an instance of one of these classes, because the driver class is loaded and registered automatically when the java.sql.DriverManager class is initialized. That typically happens on the first call to a DriverManager method such as DriverManager.getConnection. This section describes a few exceptions to this rule.
With the embedded driver, if your application shuts down
You also need to call the Class.forName method in this way if you need
to boot the
The actual driver that gets registered in the DriverManager to
handle the jdbc:derby: protocol is not the class org.apache.derby.jdbc.EmbeddedDriver
or org.apache.derby.jdbc.ClientDriver;
that class simply detects the type of
The only supported way to connect to a