Role of JDBC Driver

Direct Answer

A JDBC driver implements the JDBC contracts for a database or data source. It accepts connection details, translates JDBC operations into the vendor's protocol or API, and exposes results and errors through JDBC types. JDBC makes application structure more portable, but changing databases usually also requires changes to SQL, data types, generated-key behavior, transaction assumptions, and configuration—not only a driver swap.

Code Example

// You write standard JDBC; the driver does the vendor-specific work.
try (Connection con = DriverManager.getConnection(
        "jdbc:postgresql://localhost:5432/shop", "u", "p");
     PreparedStatement ps = con.prepareStatement("SELECT name FROM users WHERE id = ?")) {
    ps.setInt(1, 1);
    try (ResultSet rs = ps.executeQuery()) {
        // the Postgres driver turned your call into the PG wire protocol,
        // and turned the response rows back into this ResultSet
        if (rs.next()) System.out.println(rs.getString("name"));
    }
}

Common Mistakes & Pitfalls

• Thinking Java talks to the DB directly: every call goes through the driver.
• Missing the driver JAR: the code compiles but dies at runtime with No suitable driver found or ClassNotFoundException.
• Mismatched driver/DB version: an old driver against a newer server can cause subtle protocol errors.
• Confusing driver with DataSource: the DataSource hands out connections; the driver speaks the protocol underneath.