Error handling with PDO exceptions in PHP - Time & Space Complexity

Time Complexity: Error handling with PDO exceptions

O(n)

Understanding Time Complexity

When using PDO exceptions for error handling, it's important to see how the program's steps grow as input changes.

We want to know how the time to handle errors changes when running database queries.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

try {
    $pdo = new PDO($dsn, $user, $password);
    $stmt = $pdo->prepare('SELECT * FROM users WHERE id = ?');
    $stmt->execute([$userId]);
    $result = $stmt->fetchAll();
} catch (PDOException $e) {
    echo 'Error: ' . $e->getMessage();
}
    

This code tries to run a database query and catches any errors using PDO exceptions.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Fetching all rows with fetchAll() which loops through the result set.
• How many times: Once per row returned by the query, depending on the number of matching users.

How Execution Grows With Input

As the number of rows returned grows, the time to fetch all results grows too.

Input Size (n)	Approx. Operations
10	About 10 fetch steps
100	About 100 fetch steps
1000	About 1000 fetch steps

Pattern observation: The time grows roughly in direct proportion to the number of rows fetched.

Final Time Complexity

Time Complexity: O(n)

This means the time to fetch results grows linearly with the number of rows returned.

Common Mistake

[X] Wrong: "Error handling with exceptions adds a lot of extra time regardless of input size."

[OK] Correct: The exception code runs only when an error happens, so normal queries run in time based on rows fetched, not exception overhead.

Interview Connect

Understanding how error handling affects performance helps you write reliable and efficient database code, a useful skill in many projects.

Self-Check

"What if we used fetch() inside a loop instead of fetchAll()? How would the time complexity change?"

Practice

1. What is the main purpose of using try and catch blocks when working with PDO exceptions in PHP?

easy

A. To create new database tables

B. To handle database errors without stopping the entire program

C. To automatically fix SQL syntax errors

D. To speed up database queries

Solution

1. Step 1: Understand the role of try-catch

   The try block runs code that might cause an error, and catch handles that error safely.

2. Step 2: Relate to PDO exceptions

   PDO exceptions occur on database errors; using try-catch prevents the program from stopping abruptly.

3. Final Answer:

   To handle database errors without stopping the entire program -> Option B

4. Quick Check:

   try-catch handles errors safely = D [OK]

Hint: Try-catch blocks catch errors to keep programs running [OK]

Common Mistakes:

• Thinking try-catch speeds up queries
• Believing it fixes SQL errors automatically
• Confusing error handling with database creation

2. Which of the following is the correct way to set PDO to throw exceptions on errors?

easy

A. $pdo->setAttribute(PDO::ATTR_ERRMODE, PDO::ERRMODE_SILENT);

B. $pdo->setAttribute(PDO::ATTR_ERRMODE, PDO::ERRMODE_WARNING);

C. $pdo->setAttribute(PDO::ATTR_ERRMODE, PDO::ERRMODE_EXCEPTION);

D. $pdo->setAttribute(PDO::ATTR_ERRMODE, PDO::ERRMODE_IGNORE);

Solution

1. Step 1: Identify PDO error modes

   PDO supports error modes: SILENT, WARNING, EXCEPTION, and IGNORE (not standard).

2. Step 2: Choose the mode that throws exceptions

   PDO::ERRMODE_EXCEPTION makes PDO throw exceptions on errors.

3. Final Answer:

   $pdo->setAttribute(PDO::ATTR_ERRMODE, PDO::ERRMODE_EXCEPTION); -> Option C

4. Quick Check:

   Exception mode = PDO::ERRMODE_EXCEPTION = B [OK]

Hint: Use ERRMODE_EXCEPTION to get PDO exceptions [OK]

Common Mistakes:

• Using ERRMODE_SILENT which hides errors
• Confusing ERRMODE_WARNING with exceptions
• Using non-existent ERRMODE_IGNORE

3. What will be the output of this PHP code?

$pdo = new PDO('sqlite::memory:');
$pdo->setAttribute(PDO::ATTR_ERRMODE, PDO::ERRMODE_EXCEPTION);
try {
    $pdo->exec('CREATE TABLE users (id INTEGER PRIMARY KEY, name TEXT)');
    $pdo->exec('INSERT INTO users (id, name) VALUES (1, "Alice")');
    $pdo->exec('INSERT INTO users (id, name) VALUES (1, "Bob")');
    echo "Insert successful";
} catch (PDOException $e) {
    echo "Error: " . $e->getMessage();
}

medium

A. Insert successful

B. Syntax error in SQL statement

C. No output

D. Error: SQLSTATE[23000]: Integrity constraint violation: UNIQUE constraint failed: users.id

Solution

1. Step 1: Understand the code flow

   The code creates a table with a primary key on 'id' and inserts two rows with the same id=1.

2. Step 2: Identify the error

   Inserting duplicate primary keys causes an integrity constraint violation, triggering a PDOException.

3. Final Answer:

   Error: SQLSTATE[23000]: Integrity constraint violation: UNIQUE constraint failed: users.id -> Option D

4. Quick Check:

   Duplicate primary key causes exception = C [OK]

Hint: Duplicate primary keys cause PDOException errors [OK]

Common Mistakes:

• Expecting 'Insert successful' despite duplicate keys
• Thinking it's a syntax error
• Ignoring exception handling output

4. Identify the error in this PHP code snippet that uses PDO exceptions:

try {
    $pdo = new PDO('mysql:host=localhost;dbname=testdb', 'user', 'pass');
    $pdo->setAttribute(PDO::ATTR_ERRMODE, PDO::ERRMODE_EXCEPTION);
    $pdo->exec('INVALID SQL');
} catch (PDOException $e) {
    echo 'Error: ' . $e->getMessage();
}

medium

A. SQL statement is invalid causing exception

B. Error mode is not set to exceptions

C. PDO connection string is incorrect

D. Missing catch block for exceptions

Solution

1. Step 1: Check PDO connection and error mode

   The connection string and error mode setting are correct for throwing exceptions.

2. Step 2: Analyze the SQL statement

   The SQL statement 'INVALID SQL' is not valid SQL, so it triggers a PDOException.

3. Final Answer:

   SQL statement is invalid causing exception -> Option A

4. Quick Check:

   Invalid SQL causes exception = A [OK]

Hint: Invalid SQL triggers PDOException if error mode set [OK]

Common Mistakes:

• Assuming connection string is wrong
• Forgetting error mode is set correctly
• Thinking catch block is missing

5. You want to safely insert user data into a database using PDO and handle errors with exceptions. Which of the following code snippets correctly implements this with prepared statements and exception handling?

hard

A. try {
$pdo = new PDO($dsn, $user, $pass);
$pdo->setAttribute(PDO::ATTR_ERRMODE, PDO::ERRMODE_EXCEPTION);
$stmt = $pdo->prepare('INSERT INTO users (name, email) VALUES (:name, :email)');
$stmt->execute([':name' => $name, ':email' => $email]);
echo 'User added';
} catch (PDOException $e) {
echo 'Error: ' . $e->getMessage();
}

B. $pdo = new PDO($dsn, $user, $pass);
$stmt = $pdo->query('INSERT INTO users (name, email) VALUES ($name, $email)');
echo 'User added';

C. try {
$pdo = new PDO($dsn, $user, $pass);
$stmt = $pdo->prepare('INSERT INTO users (name, email) VALUES (?, ?)');
$stmt->execute([$name, $email]);
echo 'User added';
} catch (Exception $e) {
echo 'Error';
}

D. try {
$pdo = new PDO($dsn, $user, $pass);
$pdo->setAttribute(PDO::ATTR_ERRMODE, PDO::ERRMODE_WARNING);
$pdo->exec('INSERT INTO users (name, email) VALUES ("$name", "$email")');
echo 'User added';
} catch (PDOException $e) {
echo 'Error: ' . $e->getMessage();
}

Solution

1. Step 1: Check for proper error mode setting

   try { $pdo = new PDO($dsn, $user, $pass); $pdo->setAttribute(PDO::ATTR_ERRMODE, PDO::ERRMODE_EXCEPTION); $stmt = $pdo->prepare('INSERT INTO users (name, email) VALUES (:name, :email)'); $stmt->execute([':name' => $name, ':email' => $email]); echo 'User added'; } catch (PDOException $e) { echo 'Error: ' . $e->getMessage(); } sets PDO::ATTR_ERRMODE to ERRMODE_EXCEPTION, enabling exception handling.

2. Step 2: Verify use of prepared statements and parameter binding

   try { $pdo = new PDO($dsn, $user, $pass); $pdo->setAttribute(PDO::ATTR_ERRMODE, PDO::ERRMODE_EXCEPTION); $stmt = $pdo->prepare('INSERT INTO users (name, email) VALUES (:name, :email)'); $stmt->execute([':name' => $name, ':email' => $email]); echo 'User added'; } catch (PDOException $e) { echo 'Error: ' . $e->getMessage(); } uses prepared statements with named parameters and executes safely with user data.

3. Step 3: Confirm exception handling

   try { $pdo = new PDO($dsn, $user, $pass); $pdo->setAttribute(PDO::ATTR_ERRMODE, PDO::ERRMODE_EXCEPTION); $stmt = $pdo->prepare('INSERT INTO users (name, email) VALUES (:name, :email)'); $stmt->execute([':name' => $name, ':email' => $email]); echo 'User added'; } catch (PDOException $e) { echo 'Error: ' . $e->getMessage(); } catches PDOException and outputs the error message, providing safe error handling.

4. Final Answer:

   try { $pdo = new PDO($dsn, $user, $pass); $pdo->setAttribute(PDO::ATTR_ERRMODE, PDO::ERRMODE_EXCEPTION); $stmt = $pdo->prepare('INSERT INTO users (name, email) VALUES (:name, :email)'); $stmt->execute([':name' => $name, ':email' => $email]); echo 'User added'; } catch (PDOException $e) { echo 'Error: ' . $e->getMessage(); } -> Option A

5. Quick Check:

   Prepared + ERRMODE_EXCEPTION + try-catch = A [OK]

Hint: Use prepared statements with ERRMODE_EXCEPTION and try-catch [OK]

Common Mistakes:

• Not setting error mode to exceptions
• Using query() with unescaped variables
• Catching generic Exception instead of PDOException
• Using ERRMODE_WARNING which doesn't throw exceptions