AUTO_INCREMENT behavior in SQL - Cheat Sheet & Quick Revision

Recall & Review

beginner

What does AUTO_INCREMENT do in a SQL table?

AUTO_INCREMENT automatically generates a unique number for a column when a new row is added, usually used for primary keys.

intermediate

Can you insert a specific value into an AUTO_INCREMENT column?

Yes, you can insert a specific value manually, but it must not conflict with existing values to avoid errors.

intermediate

What happens if you delete the last row with the highest AUTO_INCREMENT value?

The AUTO_INCREMENT counter does not decrease automatically; new rows continue from the last highest value plus one.

advanced

How can you reset the AUTO_INCREMENT counter in MySQL?

You can reset it using: ALTER TABLE table_name AUTO_INCREMENT = value; where value is the new starting number.

beginner

Why is AUTO_INCREMENT useful in real-life applications?

It helps create unique IDs automatically, like customer IDs or order numbers, so you don’t have to manage them manually.

What type of column usually uses AUTO_INCREMENT?

A Foreign key

B Text column

C Date column

D Primary key

AUTO_INCREMENT is typically used for primary key columns to generate unique IDs automatically.

If you insert a row without specifying the AUTO_INCREMENT column, what happens?

A The column gets a unique incremented number automatically

B The insert fails

C The column is set to NULL

D The column is set to 0

When you omit the AUTO_INCREMENT column in an insert, the database assigns the next unique number automatically.

After deleting rows, what happens to the AUTO_INCREMENT counter?

A It stays the same and continues incrementing

B It resets to 1 automatically

C It decreases by the number of deleted rows

D It causes an error on next insert

Deleting rows does not reset the AUTO_INCREMENT counter; it keeps increasing from the last highest value.

How do you manually reset the AUTO_INCREMENT value in MySQL?

A UPDATE table_name SET AUTO_INCREMENT = new_value;

B ALTER TABLE table_name AUTO_INCREMENT = new_value;

C RESET AUTO_INCREMENT table_name TO new_value;

D DROP AUTO_INCREMENT FROM table_name;

The correct syntax to reset AUTO_INCREMENT in MySQL is using ALTER TABLE with AUTO_INCREMENT = new_value.

What happens if you try to insert a duplicate value into an AUTO_INCREMENT column?

A The duplicate is allowed

B The database changes the value automatically

C The insert fails with an error

D The row is ignored

Inserting a duplicate value into an AUTO_INCREMENT column causes an error because the column must be unique.

Explain how AUTO_INCREMENT works when adding new rows to a table.

Think about how IDs are assigned automatically without you typing them.

Describe how to reset the AUTO_INCREMENT counter and why you might want to do that.

Consider when you want your IDs to start fresh or from a specific number.

Practice

1. What does the AUTO_INCREMENT attribute do in a SQL table?

easy

A. Encrypts the data in the column

B. Deletes duplicate rows automatically

C. Automatically assigns a unique number to new rows

D. Prevents any new rows from being added

Solution

1. Step 1: Understand the purpose of AUTO_INCREMENT

   AUTO_INCREMENT is used to generate a unique number for each new row automatically, usually for primary keys.

2. Step 2: Compare options with this behavior

   Only Automatically assigns a unique number to new rows describes this behavior correctly; others describe unrelated actions.

3. Final Answer:

   Automatically assigns a unique number to new rows -> Option C

4. Quick Check:

   AUTO_INCREMENT = unique number assignment [OK]

Hint: AUTO_INCREMENT means unique numbers auto-assigned [OK]

Common Mistakes:

• Thinking AUTO_INCREMENT deletes duplicates
• Confusing AUTO_INCREMENT with encryption
• Assuming AUTO_INCREMENT blocks inserts

2. Which of the following is the correct syntax to create a table with an AUTO_INCREMENT column in SQL?

easy

A. CREATE TABLE users (id INT INCREMENT_AUTO, name VARCHAR(50), PRIMARY KEY(id));

B. CREATE TABLE users (id INT AUTO_INCREMENT, name VARCHAR(50), PRIMARY KEY(id));

C. CREATE TABLE users (id INT AUTO_INCREMENT PRIMARY, name VARCHAR(50));

D. CREATE TABLE users (id INT AUTO_INCREMENTED, name VARCHAR(50), PRIMARY KEY(id));

Solution

1. Step 1: Review correct AUTO_INCREMENT syntax

   The correct syntax is to declare the column as INT AUTO_INCREMENT and set it as PRIMARY KEY.

2. Step 2: Check each option for syntax errors

   CREATE TABLE users (id INT AUTO_INCREMENT, name VARCHAR(50), PRIMARY KEY(id)); matches the correct syntax. Options B, C, and D use invalid keywords or misplaced PRIMARY KEY.

3. Final Answer:

   CREATE TABLE users (id INT AUTO_INCREMENT, name VARCHAR(50), PRIMARY KEY(id)); -> Option B

4. Quick Check:

   Correct AUTO_INCREMENT syntax = CREATE TABLE users (id INT AUTO_INCREMENT, name VARCHAR(50), PRIMARY KEY(id)); [OK]

Hint: AUTO_INCREMENT goes with INT and PRIMARY KEY [OK]

Common Mistakes:

• Using wrong keywords like INCREMENT_AUTO
• Placing PRIMARY KEY inside column definition incorrectly
• Adding suffixes like AUTO_INCREMENTED

3. Given the table products with id INT AUTO_INCREMENT PRIMARY KEY and name VARCHAR(50), what will be the id values after these inserts?

INSERT INTO products (name) VALUES ('Pen');
INSERT INTO products (name) VALUES ('Pencil');
INSERT INTO products (name) VALUES ('Eraser');

medium

A. [1, 2, 3]

B. [0, 1, 2]

C. [NULL, NULL, NULL]

D. [1, 1, 1]

Solution

1. Step 1: Understand AUTO_INCREMENT numbering

   Each insert without specifying id gets the next unique number starting from 1 by default.

2. Step 2: Apply to the three inserts

   First insert gets 1, second gets 2, third gets 3 as id values.

3. Final Answer:

   [1, 2, 3] -> Option A

4. Quick Check:

   Sequential AUTO_INCREMENT IDs = [1, 2, 3] [OK]

Hint: AUTO_INCREMENT starts at 1 and increments by 1 [OK]

Common Mistakes:

• Assuming IDs start at 0
• Expecting NULL values for AUTO_INCREMENT
• Thinking IDs repeat for each insert

4. You have a table orders with order_id INT AUTO_INCREMENT PRIMARY KEY. You try to insert a row with order_id = 0 manually, but get an error. What is the likely cause?

medium

A. You cannot insert a value manually into an AUTO_INCREMENT column without special syntax

B. The table does not allow any inserts

C. The column is not set as PRIMARY KEY

D. The AUTO_INCREMENT value must be a string

Solution

1. Step 1: Understand manual inserts on AUTO_INCREMENT columns

   By default, inserting a value manually into an AUTO_INCREMENT column can cause errors unless allowed explicitly.

2. Step 2: Analyze the error cause

   The error likely occurs because the database expects to manage the AUTO_INCREMENT values automatically, and manual insertion conflicts with this.

3. Final Answer:

   You cannot insert a value manually into an AUTO_INCREMENT column without special syntax -> Option A

4. Quick Check:

   Manual insert on AUTO_INCREMENT needs care = You cannot insert a value manually into an AUTO_INCREMENT column without special syntax [OK]

Hint: AUTO_INCREMENT columns usually reject manual values [OK]

Common Mistakes:

• Assuming inserts are blocked entirely
• Confusing PRIMARY KEY with AUTO_INCREMENT behavior
• Thinking AUTO_INCREMENT accepts strings

5. A table employees has emp_id INT AUTO_INCREMENT PRIMARY KEY. After deleting the row with emp_id = 3, you insert a new row without specifying emp_id. What will be the emp_id of the new row?

hard

A. 3

B. NULL

C. 1

D. The next highest number after the last inserted ID

Solution

1. Step 1: Understand AUTO_INCREMENT behavior after deletions

   Deleting a row does not reset or reuse the deleted AUTO_INCREMENT value by default.

2. Step 2: Determine the new ID assigned

   The new row gets the next number after the highest previously assigned ID, not the deleted one.

3. Final Answer:

   The next highest number after the last inserted ID -> Option D

4. Quick Check:

   Deleted IDs are not reused automatically = The next highest number after the last inserted ID [OK]

Hint: AUTO_INCREMENT never reuses deleted IDs by default [OK]

Common Mistakes:

• Assuming deleted IDs get reused automatically
• Thinking new inserts reset to 1
• Expecting NULL for AUTO_INCREMENT columns