Why SELECT retrieves data in MySQL - Performance Analysis

Time Complexity: Why SELECT retrieves data

O(n)

Understanding Time Complexity

When we use SELECT in MySQL, the database finds and returns data from tables.

We want to understand how the time it takes grows as the data grows.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

SELECT * FROM employees WHERE department = 'Sales';

This query retrieves all employees who work in the Sales department.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Checking each row in the employees table to see if the department matches 'Sales'.
• How many times: Once for every row in the table (n times).

How Execution Grows With Input

As the number of employees grows, the database checks more rows.

Input Size (n)	Approx. Operations
10	10 checks
100	100 checks
1000	1000 checks

Pattern observation: The work grows directly with the number of rows.

Final Time Complexity

Time Complexity: O(n)

This means the time to get results grows in a straight line as the table gets bigger.

Common Mistake

[X] Wrong: "SELECT finds data instantly no matter how big the table is."

[OK] Correct: Without special help like indexes, the database must check each row one by one, so bigger tables take more time.

Interview Connect

Understanding how SELECT works helps you explain how databases handle data and why indexes matter, a useful skill in many jobs.

Self-Check

"What if we add an index on the department column? How would the time complexity change?"

Practice

1. What is the main purpose of the SELECT statement in MySQL?

easy

A. To retrieve data from one or more tables

B. To delete data from a table

C. To update existing data in a table

D. To create a new table in the database

Solution

1. Step 1: Understand the role of SELECT

   The SELECT statement is designed to fetch or retrieve data stored in tables.

2. Step 2: Compare with other SQL commands

   DELETE removes data, UPDATE changes data, and CREATE TABLE makes new tables, so these are not for retrieving data.

3. Final Answer:

   To retrieve data from one or more tables -> Option A

4. Quick Check:

   SELECT = retrieve data [OK]

Hint: SELECT always fetches data, not changes or deletes [OK]

Common Mistakes:

• Confusing SELECT with DELETE or UPDATE
• Thinking SELECT creates tables
• Assuming SELECT modifies data

2. Which of the following is the correct syntax to select all columns from a table named employees?

easy

A. SELECT employees FROM *;

B. SELECT ALL employees;

C. SELECT * FROM employees;

D. GET * FROM employees;

Solution

1. Step 1: Recall correct SELECT syntax

   The correct syntax to select all columns is SELECT * FROM table_name;.

2. Step 2: Check each option

   SELECT * FROM employees; matches the correct syntax. The other options are invalid: table name before *, using ALL incorrectly, and using GET instead of SELECT.

3. Final Answer:

   SELECT * FROM employees; -> Option C

4. Quick Check:

   SELECT * FROM table = correct syntax [OK]

Hint: Use * to select all columns in SELECT [OK]

Common Mistakes:

• Using GET instead of SELECT
• Placing table name before *
• Using ALL keyword incorrectly

3. Given the table products with columns id, name, and price, what will this query return?

SELECT name FROM products WHERE price > 100;

medium

A. All product names with price less than 100

B. All product names with price greater than 100

C. All columns for products priced over 100

D. An error because price comparison is invalid

Solution

1. Step 1: Analyze the SELECT clause

   The query selects only the name column from the products table.

2. Step 2: Understand the WHERE condition

   The condition price > 100 filters rows where price is greater than 100.

3. Final Answer:

   All product names with price greater than 100 -> Option B

4. Quick Check:

   SELECT name WHERE price > 100 = product names over 100 [OK]

Hint: WHERE filters rows; SELECT chooses columns [OK]

Common Mistakes:

• Confusing greater than with less than
• Expecting all columns instead of just name
• Thinking the query causes an error

4. Identify the error in this query:

SELECT FROM customers WHERE age > 30;

medium

A. Missing column names after SELECT

B. Incorrect WHERE clause syntax

C. Table name should be after WHERE

D. No error, query is correct

Solution

1. Step 1: Check SELECT syntax

   SELECT must be followed by column names or * to specify what to retrieve.

2. Step 2: Review the query structure

   The query has SELECT but no columns listed before FROM, which is invalid syntax.

3. Final Answer:

   Missing column names after SELECT -> Option A

4. Quick Check:

   SELECT needs columns or * [OK]

Hint: Always specify columns or * after SELECT [OK]

Common Mistakes:

• Leaving SELECT empty
• Placing table name after WHERE
• Assuming WHERE syntax is wrong

5. You want to see only the email addresses of customers who live in 'New York' from the customers table. Which query correctly retrieves this data?

hard

A. SELECT email FROM customers WHERE city == 'New York';

B. SELECT * FROM customers WHERE city = New York;

C. SELECT email WHERE city = 'New York' FROM customers;

D. SELECT email FROM customers WHERE city = 'New York';

Solution

1. Step 1: Identify correct SELECT and WHERE syntax

   The correct syntax is SELECT column FROM table WHERE condition;. The city value must be in quotes.

2. Step 2: Evaluate each option

   SELECT email FROM customers WHERE city = 'New York'; uses correct syntax and quotes around 'New York'. SELECT * FROM customers WHERE city = New York; misses quotes, causing error. SELECT email WHERE city = 'New York' FROM customers; has wrong clause order. SELECT email FROM customers WHERE city == 'New York'; uses double equals which is invalid in SQL.

3. Final Answer:

   SELECT email FROM customers WHERE city = 'New York'; -> Option D

4. Quick Check:

   Correct syntax with quotes and order [OK]

Hint: Use single quotes for string values in WHERE [OK]

Common Mistakes:

• Omitting quotes around string values
• Using == instead of = in WHERE
• Placing WHERE before FROM