Why PDO is the standard in PHP - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why use PDO for database access?

Which of the following is the main reason PDO is considered the standard for database access in PHP?

A PDO only works with MySQL databases.

B PDO automatically caches all queries for faster performance.

C PDO requires no configuration to connect to any database.

D PDO supports multiple database types with the same interface.

💡 Hint

Think about how PDO helps when switching databases.

PDO provides a consistent interface to many different databases, so you can switch databases without rewriting all your code.

❓ Predict Output

intermediate

PDO prepared statement output

What will be the output of this PHP code using PDO prepared statements?

PHP

<?php
$pdo = new PDO('sqlite::memory:');
$pdo->exec('CREATE TABLE users (id INTEGER PRIMARY KEY, name TEXT)');
$stmt = $pdo->prepare('INSERT INTO users (name) VALUES (:name)');
$stmt->execute(['name' => 'Alice']);
$stmt->execute(['name' => 'Bob']);
$count = $pdo->query('SELECT COUNT(*) FROM users')->fetchColumn();
echo $count;
?>

A 2

B 1

C 0

D SyntaxError

💡 Hint

Count how many rows were inserted.

The code inserts two users, so the count is 2.

❓ Predict Output

advanced

PDO error mode behavior

What error behavior will this PDO code produce?

PHP

<?php
$pdo = new PDO('sqlite::memory:');
$pdo->setAttribute(PDO::ATTR_ERRMODE, PDO::ERRMODE_EXCEPTION);
try {
    $pdo->exec('INVALID SQL');
    echo 'Success';
} catch (PDOException $e) {
    echo 'Error caught';
}
?>

A Success

B No output

C Error caught

D Fatal error

💡 Hint

Check how PDO handles errors with ERRMODE_EXCEPTION.

PDO throws an exception on invalid SQL when ERRMODE_EXCEPTION is set, so the catch block runs.

🧠 Conceptual

advanced

Why is PDO safer than direct queries?

Which feature of PDO helps prevent SQL injection attacks?

A Use of prepared statements with bound parameters.

B Limiting database user permissions by default.

C Automatic encryption of all data sent to the database.

D Caching query results to avoid repeated queries.

💡 Hint

Think about how user input is handled safely.

Prepared statements separate code from data, preventing malicious input from changing the query structure.

🧠 Conceptual

expert

PDO and database portability

Which statement best explains how PDO improves database portability in PHP applications?

A PDO stores all data in a single file format compatible with all databases.

B PDO provides a uniform API that works with many database systems, reducing code changes when switching databases.

C PDO requires no SQL knowledge because it uses a visual query builder internally.

D PDO automatically converts all SQL queries to the syntax of the target database.

💡 Hint

Consider how PDO abstracts database differences.

PDO offers a consistent interface for different databases, so you only need to change the connection string, not the query code.

Practice

1. Why is PDO considered the standard way to access databases in PHP?

easy

A. Because it supports prepared statements to prevent SQL injection

B. Because it only works with MySQL databases

C. Because it requires no configuration to connect to any database

D. Because it automatically creates database tables

Solution

1. Step 1: Understand PDO's security feature

   PDO uses prepared statements which separate SQL code from data, preventing attackers from injecting harmful SQL.

2. Step 2: Compare with other options

   PDO works with many databases, requires configuration, and does not create tables automatically.

3. Final Answer:

   Because it supports prepared statements to prevent SQL injection -> Option A

4. Quick Check:

   PDO security = prepared statements [OK]

Hint: Remember PDO protects with prepared statements [OK]

Common Mistakes:

• Thinking PDO only works with MySQL
• Believing PDO auto-creates tables
• Assuming PDO needs no setup

2. Which of the following is the correct way to create a PDO connection in PHP?

easy

A. $pdo = new PDO('mysql://user:pass@localhost/testdb');

B. $pdo = new PDO('mysql:host=localhost;dbname=testdb', 'user', 'pass');

C. $pdo = new PDO('connect:mysql://localhost/testdb', 'user', 'pass');

D. $pdo = new PDO('localhost', 'user', 'pass', 'testdb');

Solution

1. Step 1: Recall PDO constructor syntax

   The PDO constructor requires a DSN string like 'mysql:host=localhost;dbname=testdb' plus username and password.

2. Step 2: Check each option

   Only $pdo = new PDO('mysql:host=localhost;dbname=testdb', 'user', 'pass'); uses the correct DSN format and parameters.

3. Final Answer:

   $pdo = new PDO('mysql:host=localhost;dbname=testdb', 'user', 'pass'); -> Option B

4. Quick Check:

   PDO connection = DSN string + user/pass [OK]

Hint: DSN string format is 'driver:host=...;dbname=...' [OK]

Common Mistakes:

• Using wrong DSN format
• Passing parameters in wrong order
• Confusing DSN with URL

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

$pdo = new PDO('sqlite::memory:');
$pdo->exec('CREATE TABLE users (id INTEGER, name TEXT)');
$pdo->exec("INSERT INTO users VALUES (1, 'Alice')");
$stmt = $pdo->prepare('SELECT name FROM users WHERE id = :id');
$stmt->execute([':id' => 1]);
echo $stmt->fetchColumn();

medium

A. name

B. 1

C. Alice

D. Error: no such table

Solution

1. Step 1: Understand the code flow

   The code creates an in-memory SQLite database, a table 'users', inserts one row with id=1 and name='Alice'.

2. Step 2: Analyze the prepared statement

   The statement selects the 'name' where id=1, then fetchColumn() returns the first column of the first row, which is 'Alice'.

3. Final Answer:

   Alice -> Option C

4. Quick Check:

   PDO fetchColumn() returns 'Alice' [OK]

Hint: fetchColumn() returns first column of first row [OK]

Common Mistakes:

• Expecting the id instead of name
• Confusing fetchColumn() with fetchAll()
• Assuming table does not exist

4. Identify the error in this PDO code snippet:

$pdo = new PDO('mysql:host=localhost;dbname=testdb', 'user', 'pass');
$stmt = $pdo->prepare('SELECT * FROM users WHERE id = ?');
$stmt->execute(['id' => 5]);
$result = $stmt->fetchAll();
print_r($result);

medium

A. No error, code runs fine

B. Missing database connection

C. Wrong method name 'fetchAll' instead of 'fetch_all'

D. Using named parameter array with positional placeholder

Solution

1. Step 1: Check placeholder and execute parameter usage

   The SQL uses a positional placeholder '?', but execute() is called with an associative array ['id' => 5].

2. Step 2: Understand PDO parameter binding rules

   Positional placeholders require a numeric-indexed array, not associative keys.

3. Final Answer:

   Using named parameter array with positional placeholder -> Option D

4. Quick Check:

   Positional placeholder needs numeric array [OK]

Hint: Match placeholder type with execute() array keys [OK]

Common Mistakes:

• Mixing named and positional placeholders
• Assuming fetchAll() is misspelled
• Ignoring connection setup

5. You want to write PHP code that can switch easily between MySQL and SQLite databases without changing query code. Why is PDO the best choice for this?

hard

A. PDO provides a consistent interface and supports multiple databases with the same methods

B. PDO automatically converts MySQL queries to SQLite syntax

C. PDO requires no changes because it uses raw SQL strings only

D. PDO stores all data in memory for faster access

Solution

1. Step 1: Understand PDO's database abstraction

   PDO offers a uniform API to connect and query different databases like MySQL and SQLite.

2. Step 2: Evaluate other options

   PDO does not convert SQL syntax automatically, nor store data in memory, and raw SQL strings alone don't ensure portability.

3. Final Answer:

   PDO provides a consistent interface and supports multiple databases with the same methods -> Option A

4. Quick Check:

   PDO abstraction = easy DB switching [OK]

Hint: PDO abstracts DB differences with one API [OK]

Common Mistakes:

• Thinking PDO converts SQL syntax automatically
• Believing PDO stores data in memory
• Assuming raw SQL means no changes needed