JDBC Drivers in Java

A JDBC driver is a software component that lets a Java application talk to a specific database. It implements the JDBC interfaces (Connection, Statement, ResultSet and the rest) and translates each call into something the database understands. Drivers are traditionally grouped into four types, according to how they reach the database. This classification is a favorite interview topic. In practice, almost every driver used today is Type 4. In this lesson, you will learn the four types, their advantages and disadvantages, and how Java finds and loads a driver.

The Four Types

Type 1: JDBC-ODBC Bridge

Type 2: Native-API Driver

Oracle's OCI driver is an example.

Type 3: Network Protocol Driver

Type 4: Thin Driver

MySQL Connector/J, the PostgreSQL JDBC driver, Oracle's thin driver and the Microsoft SQL Server driver are all Type 4.

How a Driver Is Loaded

Since JDBC 4.0 (Java 6), you only put the driver's JAR on the class path. The JAR contains a small file, META-INF/services/java.sql.Driver, naming its driver class, and DriverManager loads it automatically. The old line Class.forName("com.mysql.cj.jdbc.Driver") is no longer needed.

Let's see an example that lists the registered drivers and shows what happens when no driver matches a URL:

import java.sql.Connection;
import java.sql.DatabaseMetaData;
import java.sql.Driver;
import java.sql.DriverManager;
import java.sql.SQLException;
 
public class Drivers {
    public static void main(String[] args) throws Exception {
        DriverManager.drivers().forEach(d -> System.out.println(
            "Registered: " + d.getClass().getName()
            + " (JDBC compliant: " + d.jdbcCompliant() + ")"));
 
        Driver driver = DriverManager.getDriver("jdbc:h2:mem:school");
        System.out.println("Accepts jdbc:h2:...?    "
            + driver.acceptsURL("jdbc:h2:mem:school"));
        System.out.println("Accepts jdbc:mysql:...? "
            + driver.acceptsURL("jdbc:mysql://localhost:3306/school"));
 
        try (Connection con =
                 DriverManager.getConnection("jdbc:h2:mem:school")) {
            DatabaseMetaData md = con.getMetaData();
            System.out.println(md.getDriverName() + ", JDBC "
                + md.getJDBCMajorVersion() + "." + md.getJDBCMinorVersion());
        }
 
        try {
            DriverManager.getConnection("jdbc:mysql://localhost:3306/school");
        } catch (SQLException e) {
            System.out.println("SQLException: " + e.getMessage());
        }
    }
}

Registered: org.h2.Driver (JDBC compliant: true)
Accepts jdbc:h2:...?    true
Accepts jdbc:mysql:...? false
H2 JDBC Driver, JDBC 4.3
SQLException: No suitable driver found for jdbc:mysql://localhost:3306/school

Explanation:

• DriverManager.drivers() lists every driver found on the class path. Only the H2 JAR is there, so only its driver appears.
• acceptsURL is how a driver is chosen: DriverManager asks each registered driver whether it understands the URL. H2 accepts jdbc:h2:... and rejects jdbc:mysql:....
• "No suitable driver found" is the error when no registered driver accepts the URL. It almost always means the driver JAR is missing from the class path, or the URL has a typo.

Common Drivers

Common Mistakes

Driver JAR not on the class path. "No suitable driver found for ..." is the result.

A typo in the URL prefix. jdbc:mysql//... (missing colon) matches no driver.

Using an old driver class name. MySQL's is com.mysql.cj.jdbc.Driver; the older com.mysql.jdbc.Driver is deprecated.

Interview Corner

Practice

1. Easy: For each of the four types, write one sentence saying what must be installed on the client machine.
2. Harder: Run Drivers without the H2 JAR on the class path and explain the output.

Key Takeaways