Course contentsShow
← Java
Lesson 806 of 2,87019. Exception Hierarchy and Custom ExceptionsFree lesson

SQLException: Database Access Errors

Understanding SQLException for database operations, including connection failures and query execution problems.

SQLException: Database Access Errors

You'll learn what SQLException is and when Java throws it during database operations.

What Is SQLException?

SQLException is a checked exception that Java throws when something goes wrong while your program interacts with a database. Just like IOException signals file or stream problems, SQLException tells you that a database operation has failed. Since it's checked, you must either catch it or declare it with throws.

Think of SQLException as a red flag raised by the database: "I couldn't do what you asked!" It might be a connection issue, a malformed query, or a permission problem.

Common Causes of SQLException

Database operations can fail in many ways:

  • Connection failures: The database server is unreachable, credentials are wrong, or the database doesn't exist
  • Query execution errors: Your SQL statement has syntax errors or references tables/columns that don't exist
  • Constraint violations: Inserting duplicate keys or violating foreign key rules
  • Timeout issues: The database took too long to respond
  • Closed connections: Trying to use a connection that's already been closed

Handling SQLException

Because SQLException is checked, you must handle it explicitly:

public void connectToDatabase() throws SQLException {
    // Database code that might fail
    // Caller must handle SQLException
}

public void safeConnect() {
    try {
        // Attempt database connection
        // Execute queries
    } catch (SQLException e) {
        System.err.println("Database error: " + e.getMessage());
        e.printStackTrace();
    }
}

SQLException provides helpful methods like getSQLState() and getErrorCode() to identify the specific database problem.

Key Takeaway: SQLException is a checked exception for database operation failures, requiring explicit handling to deal with connection issues, query errors, and other database-related problems.