INSERT INTO multiple rows in MySQL - Time & Space Complexity

Time Complexity: INSERT INTO multiple rows

O(n)

Understanding Time Complexity

When adding many rows to a database table at once, it's important to know how the time to insert grows as we add more rows.

We want to understand how the cost changes when inserting multiple rows in one command.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

INSERT INTO employees (name, age, department) VALUES
  ('Alice', 30, 'HR'),
  ('Bob', 25, 'Sales'),
  ('Charlie', 28, 'IT');
    

This code inserts three new employee records into the employees table in a single statement.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Inserting each row into the table.
• How many times: Once per row being inserted (here 3 times).

How Execution Grows With Input

Each additional row adds roughly one more insert operation.

Input Size (n)	Approx. Operations
10	About 10 insert operations
100	About 100 insert operations
1000	About 1000 insert operations

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

Final Time Complexity

Time Complexity: O(n)

This means the time to insert grows in a straight line as you add more rows.

Common Mistake

[X] Wrong: "Inserting multiple rows at once takes the same time as inserting just one row."

[OK] Correct: Each row still needs to be added, so more rows mean more work and more time.

Interview Connect

Understanding how insert time grows helps you explain database performance clearly and shows you know how data size affects operations.

Self-Check

"What if we inserted rows one by one in separate statements instead? How would the time complexity change?"

Practice

1. What does the INSERT INTO statement with multiple rows do in MySQL?

easy

A. Updates multiple rows at once

B. Adds several records to a table in one command

C. Deletes multiple rows from a table

D. Creates a new table with multiple rows

Solution

1. Step 1: Understand the purpose of INSERT INTO

   The INSERT INTO statement is used to add new data into a table.

2. Step 2: Recognize multiple rows insertion

   When multiple rows are inserted, several sets of values are added in one command, saving time.

3. Final Answer:

   Adds several records to a table in one command -> Option B

4. Quick Check:

   Multiple rows insertion = Adds many records [OK]

Hint: Multiple rows use commas between parentheses [OK]

Common Mistakes:

• Confusing INSERT with DELETE or UPDATE
• Thinking it creates a new table
• Believing it modifies existing rows

2. Which of the following is the correct syntax to insert multiple rows into a table named students with columns id and name?

easy

A. INSERT INTO students (id, name) VALUES (1, 'Alice'), (2, 'Bob');

B. INSERT INTO students VALUES (1, 'Alice'); (2, 'Bob');

C. INSERT INTO students (id, name) VALUES (1, 'Alice') AND (2, 'Bob');

D. INSERT INTO students (id, name) SET (1, 'Alice'), (2, 'Bob');

Solution

1. Step 1: Check the correct use of VALUES and parentheses

   The correct syntax uses VALUES followed by multiple sets of values in parentheses separated by commas.

2. Step 2: Identify the correct option

   INSERT INTO students (id, name) VALUES (1, 'Alice'), (2, 'Bob'); correctly uses VALUES (1, 'Alice'), (2, 'Bob') with commas separating rows.

3. Final Answer:

   INSERT INTO students (id, name) VALUES (1, 'Alice'), (2, 'Bob'); -> Option A

4. Quick Check:

   VALUES + multiple parentheses + commas = correct syntax [OK]

Hint: Use VALUES with comma-separated parentheses for rows [OK]

Common Mistakes:

• Using semicolons between rows instead of commas
• Using AND instead of commas
• Using SET instead of VALUES

3. Given the table products(id INT, name VARCHAR(20)), what will be the result of this query?

INSERT INTO products (id, name) VALUES (1, 'Pen'), (2, 'Pencil');
SELECT * FROM products;

medium

A. [{id:1, name:'Pen'}]

B. Syntax error due to missing commas

C. [{id:1, name:'Pen'}, {id:2, name:'Pencil'}]

D. Empty result, no rows inserted

Solution

1. Step 1: Understand the INSERT query

   The query inserts two rows: one with id=1 and name='Pen', another with id=2 and name='Pencil'.

2. Step 2: Understand the SELECT query

   The SELECT query fetches all rows from the table, so it will show both inserted rows.

3. Final Answer:

   [{id:1, name:'Pen'}, {id:2, name:'Pencil'}] -> Option C

4. Quick Check:

   Multiple rows inserted = multiple rows returned [OK]

Hint: Multiple rows inserted appear in SELECT output [OK]

Common Mistakes:

• Assuming only one row inserts
• Thinking syntax error occurs without commas
• Believing no rows are inserted

4. Identify the error in this query:

INSERT INTO employees (id, name) VALUES (1, 'John') (2, 'Jane');

medium

A. Extra semicolon inside VALUES

B. Using single quotes instead of double quotes

C. Missing column names

D. Missing comma between row values

Solution

1. Step 1: Check syntax for multiple rows insertion

   Multiple rows must be separated by commas between parentheses.

2. Step 2: Identify the missing comma

   The query misses a comma between (1, 'John') and (2, 'Jane').

3. Final Answer:

   Missing comma between row values -> Option D

4. Quick Check:

   Rows separated by commas, not just spaces [OK]

Hint: Separate each row with a comma inside VALUES [OK]

Common Mistakes:

• Omitting commas between rows
• Confusing quotes usage
• Forgetting column list

5. You want to insert multiple rows into a table orders(order_id, product, quantity). You have this query:

INSERT INTO orders (order_id, product, quantity) VALUES (101, 'Book', 2), (102, 'Pen', 5), (101, 'Notebook', 3);

What problem might occur and how to fix it?

hard

A. Duplicate order_id 101 may cause error if order_id is PRIMARY KEY; fix by using unique IDs

B. Missing commas between rows; fix by adding commas

C. Wrong column order; fix by rearranging columns

D. Using single quotes for strings; fix by using double quotes

Solution

1. Step 1: Identify duplicate primary key values

   If order_id is a PRIMARY KEY, duplicate values like 101 cause insertion errors.

2. Step 2: Fix by ensuring unique keys

   Use unique order_id values for each row to avoid conflicts.

3. Final Answer:

   Duplicate order_id 101 may cause error if order_id is PRIMARY KEY; fix by using unique IDs -> Option A

4. Quick Check:

   Primary keys must be unique [OK]

Hint: Primary keys must be unique in multiple inserts [OK]

Common Mistakes:

• Ignoring duplicate primary key errors
• Confusing commas with semicolons
• Misunderstanding string quoting rules