Savepoints in MySQL - Time & Space Complexity

Time Complexity: Savepoints

O(n)

Understanding Time Complexity

When using savepoints in MySQL, we want to understand how the time to manage these points grows as we add more savepoints or operations.

We ask: How does the cost of setting, rolling back, or releasing savepoints change with more savepoints?

Scenario Under Consideration

Analyze the time complexity of the following MySQL savepoint usage.

START TRANSACTION;
SAVEPOINT sp1;
-- some SQL operations
SAVEPOINT sp2;
-- more SQL operations
ROLLBACK TO SAVEPOINT sp1;
RELEASE SAVEPOINT sp2;
COMMIT;
    

This code sets two savepoints, performs operations, rolls back to the first savepoint, releases the second, then commits.

Identify Repeating Operations

Look for repeated actions that affect time.

• Primary operation: Setting, rolling back, and releasing savepoints.
• How many times: Each savepoint operation happens once per savepoint used.

How Execution Grows With Input

As you add more savepoints, each savepoint command takes roughly the same time.

Number of Savepoints (n)	Approx. Operations
10	About 10 savepoint operations
100	About 100 savepoint operations
1000	About 1000 savepoint operations

Pattern observation: The time grows directly with the number of savepoint commands used.

Final Time Complexity

Time Complexity: O(n)

This means the time to manage savepoints grows linearly with how many savepoints you use.

Common Mistake

[X] Wrong: "Rolling back to a savepoint takes constant time no matter how many savepoints exist."

[OK] Correct: Rolling back must find the savepoint in the list, so time grows with the number of savepoints.

Interview Connect

Understanding how savepoints affect performance helps you write efficient transactions and shows you know how databases handle partial rollbacks.

Self-Check

"What if we nested savepoints inside loops? How would that affect the time complexity?"

Practice

1. What is the main purpose of a SAVEPOINT in MySQL transactions?

easy

A. To start a new transaction automatically

B. To permanently save changes to the database

C. To mark a point in a transaction to which you can roll back later

D. To commit all changes immediately

Solution

1. Step 1: Understand what a savepoint does

   A savepoint marks a specific point inside a transaction to which you can roll back without affecting earlier changes.

2. Step 2: Differentiate from commit and start

   Unlike commit, which saves all changes permanently, savepoints allow partial rollback. It does not start a new transaction.

3. Final Answer:

   To mark a point in a transaction to which you can roll back later -> Option C

4. Quick Check:

   Savepoint = partial rollback marker [OK]

Hint: Savepoints let you undo part of a transaction, not all [OK]

Common Mistakes:

• Confusing savepoint with commit
• Thinking savepoint starts a new transaction
• Assuming savepoint permanently saves changes

2. Which of the following is the correct syntax to create a savepoint named sp1 in MySQL?

easy

A. SAVEPOINT sp1;

B. CREATE SAVEPOINT sp1;

C. SET SAVEPOINT sp1;

D. BEGIN SAVEPOINT sp1;

Solution

1. Step 1: Recall MySQL savepoint syntax

   The correct syntax to create a savepoint is simply SAVEPOINT savepoint_name;.

2. Step 2: Check other options for correctness

   Options B, C, and D use incorrect keywords like CREATE, SET, or BEGIN which are not used for savepoints.

3. Final Answer:

   SAVEPOINT sp1; -> Option A

4. Quick Check:

   Savepoint syntax = SAVEPOINT name; [OK]

Hint: Use just SAVEPOINT plus name to create one [OK]

Common Mistakes:

• Adding CREATE or SET before SAVEPOINT
• Using BEGIN with SAVEPOINT
• Missing semicolon at end

3. Consider this transaction sequence:

START TRANSACTION;
INSERT INTO accounts VALUES (1, 100);
SAVEPOINT sp1;
UPDATE accounts SET balance = 200 WHERE id = 1;
ROLLBACK TO SAVEPOINT sp1;
COMMIT;

What will be the final balance for account with id=1?

medium

A. 100

B. 200

C. 0

D. NULL

Solution

1. Step 1: Follow the transaction steps

   First, a row with balance 100 is inserted. Then a savepoint sp1 is created. Next, balance is updated to 200.

2. Step 2: Rollback to savepoint sp1

   Rolling back to sp1 undoes the update but keeps the insert. So balance returns to 100.

3. Final Answer:

   100 -> Option A

4. Quick Check:

   Rollback to savepoint undoes changes after it [OK]

Hint: Rollback to savepoint undoes later changes only [OK]

Common Mistakes:

• Thinking rollback undoes entire transaction
• Assuming balance stays 200 after rollback
• Confusing commit effects

4. What is wrong with this MySQL transaction code?

START TRANSACTION;
SAVEPOINT sp1;
ROLLBACK TO sp2;
COMMIT;

medium

A. You must commit before creating a savepoint

B. ROLLBACK TO requires a semicolon after savepoint name

C. SAVEPOINT must come after ROLLBACK

D. You cannot rollback to a savepoint that was not created

Solution

1. Step 1: Check savepoint creation

   The code creates savepoint sp1 but tries to rollback to sp2 which does not exist.

2. Step 2: Understand rollback to savepoint rules

   You can only rollback to savepoints that were previously created in the current transaction.

3. Final Answer:

   You cannot rollback to a savepoint that was not created -> Option D

4. Quick Check:

   Rollback to unknown savepoint = error [OK]

Hint: Rollback only to existing savepoints in current transaction [OK]

Common Mistakes:

• Trying to rollback to a non-existent savepoint
• Misordering savepoint and rollback commands
• Assuming semicolon placement causes error

5. You want to update multiple rows in a transaction but be able to undo only the last two updates if needed. Which sequence correctly uses savepoints to achieve this?

hard

A. START TRANSACTION; SAVEPOINT sp1; UPDATE row1; SAVEPOINT sp2; UPDATE row2; UPDATE row3; ROLLBACK TO sp2; COMMIT;

B. START TRANSACTION; UPDATE row1; SAVEPOINT sp1; UPDATE row2; SAVEPOINT sp2; UPDATE row3; ROLLBACK TO sp1; COMMIT;

C. START TRANSACTION; UPDATE row1; UPDATE row2; SAVEPOINT sp1; UPDATE row3; ROLLBACK TO sp1; COMMIT;

D. START TRANSACTION; UPDATE row1; SAVEPOINT sp1; UPDATE row2; SAVEPOINT sp2; UPDATE row3; ROLLBACK TO sp2; COMMIT;

Solution

1. Step 1: Understand the goal

   You want to undo only the last two updates, meaning updates to row2 and row3, but keep update to row1.

2. Step 2: Analyze each option

   START TRANSACTION; UPDATE row1; SAVEPOINT sp1; UPDATE row2; SAVEPOINT sp2; UPDATE row3; ROLLBACK TO sp2; COMMIT;: START TRANSACTION; UPDATE row1; SAVEPOINT sp1; UPDATE row2; SAVEPOINT sp2; UPDATE row3; ROLLBACK TO sp2; COMMIT; sets sp1 after row1 update, sp2 after row2 update, then updates row3. Rolling back to sp2 undoes only the update to row3, keeping updates to row1 and row2.

3. Step 3: Re-examine options carefully

   START TRANSACTION; UPDATE row1; SAVEPOINT sp1; UPDATE row2; SAVEPOINT sp2; UPDATE row3; ROLLBACK TO sp1; COMMIT; rolls back to sp1, undoing updates to row2 and row3, which matches the goal of undoing last two updates.

4. Final Answer:

   START TRANSACTION; UPDATE row1; SAVEPOINT sp1; UPDATE row2; SAVEPOINT sp2; UPDATE row3; ROLLBACK TO sp1; COMMIT; -> Option B

5. Quick Check:

   Rollback to earlier savepoint undoes all later changes [OK]

Hint: Rollback to savepoint before last two updates to undo them [OK]

Common Mistakes:

• Rolling back to wrong savepoint
• Not placing savepoints after each update
• Confusing which updates get undone