Why prepared statements exist in SQL - See It in Action

Understanding Why Prepared Statements Exist

📖 Scenario: You are working on a small online bookstore database. You want to safely and efficiently search for books by their title.

🎯 Goal: Build a simple SQL query using prepared statements to safely search for books by title, preventing SQL injection and improving performance.

📋 What You'll Learn

Create a table called books with columns id (integer), title (text), and author (text).

Insert three specific books into the books table.

Write a prepared statement to select books by title using a placeholder.

Execute the prepared statement with a specific book title.

💡 Why This Matters

🌍 Real World

Prepared statements are used in web applications to safely handle user input in database queries, preventing attacks and improving speed.

💼 Career

Understanding prepared statements is essential for database developers, backend engineers, and anyone working with databases to write secure and efficient code.

1

Create the books table and insert data

Write SQL commands to create a table called books with columns id (integer), title (text), and author (text). Then insert these three books exactly: (1, 'The Great Gatsby', 'F. Scott Fitzgerald'), (2, '1984', 'George Orwell'), and (3, 'To Kill a Mockingbird', 'Harper Lee').

SQL

-- Create the books table and insert three books
-- Your code here

Hint

Use CREATE TABLE to define the table and INSERT INTO to add each book.

2

Prepare a statement to select books by title

Write a SQL command to prepare a statement named find_book that selects all columns from books where the title equals a placeholder ?.

SQL

CREATE TABLE books (id INTEGER, title TEXT, author TEXT);
INSERT INTO books VALUES (1, 'The Great Gatsby', 'F. Scott Fitzgerald');
INSERT INTO books VALUES (2, '1984', 'George Orwell');
INSERT INTO books VALUES (3, 'To Kill a Mockingbird', 'Harper Lee');
-- Prepare the statement named find_book
-- Your code here

Hint

Use PREPARE find_book FROM 'SELECT * FROM books WHERE title = ?' to create the prepared statement.

3

Execute the prepared statement with a book title

Write a SQL command to execute the prepared statement find_book with the parameter '1984'.

SQL

CREATE TABLE books (id INTEGER, title TEXT, author TEXT);
INSERT INTO books VALUES (1, 'The Great Gatsby', 'F. Scott Fitzgerald');
INSERT INTO books VALUES (2, '1984', 'George Orwell');
INSERT INTO books VALUES (3, 'To Kill a Mockingbird', 'Harper Lee');
PREPARE find_book FROM 'SELECT * FROM books WHERE title = ?';
-- Execute the prepared statement with '1984'
-- Your code here

Hint

Use EXECUTE find_book USING '1984' to run the prepared statement with the title.

4

Deallocate the prepared statement

Write a SQL command to deallocate the prepared statement named find_book to free resources.

SQL

CREATE TABLE books (id INTEGER, title TEXT, author TEXT);
INSERT INTO books VALUES (1, 'The Great Gatsby', 'F. Scott Fitzgerald');
INSERT INTO books VALUES (2, '1984', 'George Orwell');
INSERT INTO books VALUES (3, 'To Kill a Mockingbird', 'Harper Lee');
PREPARE find_book FROM 'SELECT * FROM books WHERE title = ?';
EXECUTE find_book USING '1984';
-- Deallocate the prepared statement find_book
-- Your code here

Hint

Use DEALLOCATE PREPARE find_book; to clean up the prepared statement.

Practice

1. Why do prepared statements exist in SQL?
Prepared statements help mainly to:

easy

A. Separate the SQL command from the data to improve security and performance

B. Allow writing SQL queries without any parameters

C. Automatically create database tables

D. Encrypt the entire database

Solution

1. Step 1: Understand the purpose of prepared statements

   Prepared statements separate the SQL command from the data values, which helps prevent SQL injection attacks and improves performance when running similar queries multiple times.

2. Step 2: Evaluate the options

   Only Separate the SQL command from the data to improve security and performance correctly describes this purpose. The other options describe unrelated or incorrect uses.

3. Final Answer:

   Separate the SQL command from the data to improve security and performance -> Option A

4. Quick Check:

   Prepared statements = separate command and data [OK]

Hint: Prepared statements separate code and data for safety [OK]

Common Mistakes:

• Thinking prepared statements create tables
• Believing they encrypt the database
• Confusing them with simple SQL queries without parameters

2. Which of the following is the correct syntax to prepare a statement in SQL?
Assume a table named users with columns id and name.

easy

A. PREPARE stmt FROM 'SELECT * FROM users WHERE id = ?';

B. PREPARE stmt AS SELECT * FROM users WHERE id = ?;

C. PREPARE stmt TO 'SELECT * FROM users WHERE id = ?';

D. PREPARE stmt SELECT * FROM users WHERE id = ?;

Solution

1. Step 1: Recall the standard syntax for preparing statements

   The correct syntax uses PREPARE statement_name FROM 'SQL query with placeholders';

2. Step 2: Match the options to the syntax

   PREPARE stmt FROM 'SELECT * FROM users WHERE id = ?'; matches the correct syntax exactly. The other options use incorrect keywords or omit necessary parts.

3. Final Answer:

   PREPARE stmt FROM 'SELECT * FROM users WHERE id = ?'; -> Option A

4. Quick Check:

   PREPARE ... FROM 'query' is correct syntax [OK]

Hint: Remember: PREPARE name FROM 'query' [OK]

Common Mistakes:

• Using AS instead of FROM
• Omitting quotes around the query
• Leaving out the placeholder symbol '?'

3. Given the prepared statement:

PREPARE stmt FROM 'SELECT name FROM users WHERE id = ?';
EXECUTE stmt USING @user_id;

If @user_id = 5 and the users table has a row with id=5 and name='Alice', what will be the output?

medium

A. Returns an error because of missing quotes

B. Returns the name 'Alice'

C. Returns all user names

D. Returns no rows

Solution

1. Step 1: Understand the prepared statement execution

   The statement selects the name from users where id equals the parameter. The parameter @user_id is set to 5.

2. Step 2: Check the data and query result

   Since the users table has a row with id=5 and name='Alice', the query returns 'Alice'.

3. Final Answer:

   Returns the name 'Alice' -> Option B

4. Quick Check:

   Parameter 5 matches id=5, returns 'Alice' [OK]

Hint: Prepared statement returns matching row for parameter [OK]

Common Mistakes:

• Assuming it returns all rows
• Thinking it causes syntax error
• Ignoring the parameter value

4. You wrote this code:

PREPARE stmt FROM 'SELECT * FROM users WHERE id = ?';
EXECUTE stmt USING 5;

But it gives an error. What is the likely cause?

medium

A. The placeholder '?' is not allowed in prepared statements

B. PREPARE statement is missing a semicolon

C. EXECUTE requires a user variable, not a direct value

D. The table users does not exist

Solution

1. Step 1: Identify the error in EXECUTE syntax

   EXECUTE expects user variables (like @var), not direct literal values.

2. Step 2: Understand correct usage

   You must assign 5 to a user variable (e.g., SET @id=5;) and then EXECUTE stmt USING @id;

3. Final Answer:

   EXECUTE requires a user variable, not a direct value -> Option C

4. Quick Check:

   EXECUTE needs variables, not literals [OK]

Hint: EXECUTE needs user variables, not direct values [OK]

Common Mistakes:

• Passing direct values instead of variables
• Missing semicolon is usually not the cause
• Assuming '?' is invalid in prepared statements

5. You want to run the query SELECT * FROM orders WHERE customer_id = ? AND status = ? multiple times with different values. Why is using a prepared statement better than building the query each time with string concatenation?

hard

A. Prepared statements encrypt the query parameters

B. Prepared statements automatically update the database schema

C. String concatenation is faster and safer than prepared statements

D. Prepared statements prevent SQL injection and improve performance by reusing the query plan

Solution

1. Step 1: Understand the benefits of prepared statements

   Prepared statements separate data from code, preventing harmful input (SQL injection) and allow the database to reuse the compiled query plan for speed.

2. Step 2: Compare with string concatenation

   Building queries by concatenating strings risks injection attacks and forces the database to parse each query anew, reducing performance.

3. Final Answer:

   Prepared statements prevent SQL injection and improve performance by reusing the query plan -> Option D

4. Quick Check:

   Prepared statements = safer + faster reuse [OK]

Hint: Prepared statements = safer + faster repeated queries [OK]

Common Mistakes:

• Thinking string concatenation is safer
• Believing prepared statements change schema
• Assuming prepared statements encrypt data