![]() ![]() The driver manager can load appropriate driver based on the database connection URL. Or if the JDBC client connects to Derby server on a remote machine, go with the network client driver.If you are using Java 5.0 or earlier, you have to load the driver explicitly like this: Class.forName(".EmbeddedDriver") Or: DriverManager.registerDriver(new .EmbeddedDriver()) However, since Java 6.0 or later, loading JDBC driver as such becomes optional. ![]() So if you are planning to use everything of Derby in one machine, go with the embedded driver.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |