Auto-commit behavior in SQL - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is auto-commit behavior in SQL databases?

Auto-commit behavior means that every SQL statement is treated as a complete transaction and is automatically saved (committed) to the database without needing an explicit commit command.

beginner

How does auto-commit affect data changes in a database?

With auto-commit on, each change is immediately saved and visible to others. If auto-commit is off, changes stay temporary until you explicitly commit them.

intermediate

How can you turn off auto-commit in SQL?

You can turn off auto-commit by using commands like SET autocommit=0; in MySQL or by starting a transaction explicitly with BEGIN TRANSACTION; in many databases.

intermediate

Why might you want to disable auto-commit?

Disabling auto-commit lets you group multiple SQL statements into one transaction, so you can commit them all together or roll them back if something goes wrong, ensuring data consistency.

intermediate

What happens if an error occurs during a transaction when auto-commit is off?

If auto-commit is off and an error happens, you can roll back the entire transaction to undo all changes made since the transaction started, preventing partial updates.

What does auto-commit do in SQL?

A Deletes all data after each statement

B Prevents any changes from being saved

C Automatically saves each SQL statement as a transaction

D Requires manual commit after every statement

Auto-commit automatically saves each SQL statement as a transaction without needing a manual commit.

How do you disable auto-commit in MySQL?

A SET autocommit=0;

B COMMIT;

C ROLLBACK;

D START TRANSACTION;

The command SET autocommit=0; disables auto-commit in MySQL.

If auto-commit is off, what must you do to save changes?

A Run SELECT statement

B Use COMMIT command

C Use ROLLBACK command

D Nothing, changes save automatically

When auto-commit is off, you must use COMMIT to save changes permanently.

What is a benefit of turning off auto-commit?

A Group multiple statements into one transaction

B Automatically delete old data

C Speed up query execution

D Prevent any data changes

Turning off auto-commit lets you group multiple statements into a single transaction for better control.

What happens if an error occurs during a transaction with auto-commit off?

A All changes are saved anyway

B The error is ignored

C The database shuts down

D You can roll back all changes made in the transaction

With auto-commit off, you can roll back the entire transaction if an error occurs to avoid partial updates.

Explain what auto-commit behavior means in SQL and how it affects transactions.

Think about when changes become permanent in the database.

Describe why and how you would disable auto-commit in a database session.

Consider scenarios where you want to save or undo multiple changes together.

Practice

1. What does auto-commit mode do in a SQL database?

easy

A. Prevents any changes from being saved to the database

B. Requires manual saving of changes after multiple statements

C. Automatically saves each SQL statement immediately after execution

D. Only saves changes when the database server restarts

Solution

1. Step 1: Understand auto-commit behavior

   Auto-commit means every SQL statement is saved immediately without needing extra commands.

2. Step 2: Compare options with definition

   Automatically saves each SQL statement immediately after execution matches this behavior exactly, others describe manual or no saving.

3. Final Answer:

   Automatically saves each SQL statement immediately after execution -> Option C

4. Quick Check:

   Auto-commit = immediate save [OK]

Hint: Auto-commit means no manual save needed after each statement [OK]

Common Mistakes:

• Thinking auto-commit requires manual COMMIT
• Confusing auto-commit with rollback behavior
• Assuming changes save only on server restart

2. Which SQL command turns off auto-commit mode in most databases?

easy

A. COMMIT;

B. SAVEPOINT;

C. ROLLBACK;

D. SET AUTOCOMMIT = OFF;

Solution

1. Step 1: Identify command to disable auto-commit

   Most databases use SET AUTOCOMMIT = OFF; to disable auto-commit mode.

2. Step 2: Understand other commands

   COMMIT saves changes, ROLLBACK undoes changes, SAVEPOINT marks a point in a transaction; none disable auto-commit.

3. Final Answer:

   SET AUTOCOMMIT = OFF; -> Option D

4. Quick Check:

   Disable auto-commit = SET AUTOCOMMIT = OFF [OK]

Hint: SET AUTOCOMMIT = OFF disables auto-commit [OK]

Common Mistakes:

• Using COMMIT or ROLLBACK to disable auto-commit
• Confusing SAVEPOINT with auto-commit control
• Omitting the SET keyword

3. Consider this sequence with auto-commit OFF:
INSERT INTO users (id, name) VALUES (1, 'Alice');
ROLLBACK;
SELECT * FROM users WHERE id = 1;
What will the SELECT query return?

medium

A. A row with id=1 and name='Alice'

B. No rows

C. Syntax error

D. All rows in users table

Solution

1. Step 1: Analyze the INSERT and ROLLBACK with auto-commit OFF

   With auto-commit OFF, the INSERT is not saved until COMMIT. ROLLBACK undoes the INSERT.

2. Step 2: Determine SELECT result after rollback

   Since the INSERT was undone, the SELECT finds no row with id=1.

3. Final Answer:

   No rows -> Option B

4. Quick Check:

   ROLLBACK undoes changes, so SELECT returns no rows [OK]

Hint: ROLLBACK undoes uncommitted changes, so no new rows appear [OK]

Common Mistakes:

• Assuming INSERT is saved without COMMIT
• Thinking ROLLBACK only affects future queries
• Expecting syntax error from ROLLBACK

4. You run these commands with auto-commit OFF:
UPDATE products SET price = price * 0.9 WHERE category = 'Books';
COMMIT;
ROLLBACK;
What is the state of the prices after these commands?

medium

A. Prices are updated with 10% discount

B. Prices remain unchanged

C. Syntax error due to ROLLBACK after COMMIT

D. Partial update applied

Solution

1. Step 1: Understand effect of UPDATE and COMMIT

   UPDATE changes prices, COMMIT saves these changes permanently.

2. Step 2: Analyze ROLLBACK after COMMIT

   ROLLBACK after COMMIT has no effect because changes are already saved.

3. Final Answer:

   Prices are updated with 10% discount -> Option A

4. Quick Check:

   COMMIT saves changes; ROLLBACK after does nothing [OK]

Hint: COMMIT saves changes; ROLLBACK after commit does nothing [OK]

Common Mistakes:

• Thinking ROLLBACK undoes committed changes
• Assuming partial updates without commit
• Confusing syntax error with command order

5. You want to insert multiple rows into a table but only save them if all inserts succeed. Which approach correctly uses auto-commit behavior?

hard

A. Turn auto-commit OFF, insert all rows, then COMMIT if no errors

B. Keep auto-commit ON and insert rows one by one without COMMIT

C. Use ROLLBACK before inserting rows to save them all

D. Insert rows and rely on auto-commit to undo on error automatically

Solution

1. Step 1: Understand transactional control with auto-commit OFF

   Turning auto-commit OFF lets you group multiple inserts into one transaction.

2. Step 2: Use COMMIT to save only if all inserts succeed

   After all inserts, COMMIT saves changes; if errors occur, ROLLBACK can undo all.

3. Final Answer:

   Turn auto-commit OFF, insert all rows, then COMMIT if no errors -> Option A

4. Quick Check:

   Group inserts with auto-commit OFF and COMMIT [OK]

Hint: Turn off auto-commit to group inserts, then COMMIT [OK]

Common Mistakes:

• Relying on auto-commit ON for grouped inserts
• Using ROLLBACK before inserts to save changes
• Expecting auto-commit to undo on error automatically