Why PDO is the standard in PHP - Performance Analysis

Time Complexity: Why PDO is the standard

O(n)

Understanding Time Complexity

When using PHP to work with databases, the way we connect and run queries affects how fast our code runs as data grows.

We want to understand how using PDO (PHP Data Objects) impacts the time it takes to execute database operations.

Scenario Under Consideration

Analyze the time complexity of this PDO code snippet.

// Connect to database using PDO
$pdo = new PDO('mysql:host=localhost;dbname=testdb', 'user', 'pass');

// Prepare a query
$stmt = $pdo->prepare('SELECT * FROM users WHERE age > :age');

// Execute query with parameter
$stmt->execute(['age' => 18]);

// Fetch all results
$results = $stmt->fetchAll(PDO::FETCH_ASSOC);

This code connects to a database, prepares a query with a condition, runs it, and fetches all matching rows.

Identify Repeating Operations

Look at what repeats or takes time in this process.

• Primary operation: Fetching all rows from the database after query execution.
• How many times: Once per row returned, the fetchAll method processes each row internally.

How Execution Grows With Input

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

Input Size (n)	Approx. Operations
10	Processes about 10 rows
100	Processes about 100 rows
1000	Processes about 1000 rows

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

Final Time Complexity

Time Complexity: O(n)

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

Common Mistake

[X] Wrong: "Using PDO makes queries run instantly no matter how much data there is."

[OK] Correct: PDO helps organize and secure queries, but fetching more data still takes more time because each row must be processed.

Interview Connect

Understanding how PDO handles data fetching helps you explain how your code scales with data size, a key skill in real projects and interviews.

Self-Check

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

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