Why UPDATE needs caution in SQL - Visual Breakdown

Concept Flow - Why UPDATE needs caution

Start UPDATE command

↓

Check WHERE condition

↓

Update row

↓

Repeat for next row

↓

End UPDATE

The UPDATE command checks each row against the WHERE condition. If true, it updates the row; if false, it skips. This repeats for all rows.

Execution Sample

SQL

UPDATE employees
SET salary = salary * 1.1
WHERE department = 'Sales';

This increases salary by 10% only for employees in the Sales department.

Execution Table

Step	Row ID	Current salary	Condition (department='Sales')	Action	New salary
1	101	50000	True	Update salary	55000
2	102	60000	False	Skip	60000
3	103	55000	True	Update salary	60500
4	104	70000	False	Skip	70000
5	105	48000	True	Update salary	52800
6	-	-	-	-	-
Exit	-	-	No more rows	Stop	-

💡 All rows checked; UPDATE ends.

Variable Tracker

Variable	Start	After 1	After 2	After 3	After 4	After 5	Final
salary_101	50000	55000	55000	55000	55000	55000	55000
salary_102	60000	60000	60000	60000	60000	60000	60000
salary_103	55000	55000	60500	60500	60500	60500	60500
salary_104	70000	70000	70000	70000	70000	70000	70000
salary_105	48000	48000	48000	48000	52800	52800	52800

Key Moments - 3 Insights

Why is the WHERE clause important in UPDATE?

Without WHERE, all rows update (see execution_table rows 2 and 4 where condition is False and rows are skipped). This can cause unintended changes.

What happens if the condition is always True?

All rows get updated, which might not be desired. The exit_note and execution_table show UPDATE runs on every row if condition is True.

Why do some rows keep their original salary?

Because their department is not 'Sales', so condition is False and action is Skip (rows 2 and 4). This shows selective updating.

Visual Quiz - 3 Questions

Look at the execution_table, what is the new salary of row ID 103 after step 3?

A 55000

B 60500

C 60000

D 70000

💡 Hint

Check row 3 in execution_table under 'New salary' column.

At which step does the UPDATE skip a row due to the condition being False?

A Step 2

B Step 3

C Step 1

D Step 5

💡 Hint

Look at execution_table rows where 'Condition' is False and 'Action' is Skip.

If the WHERE clause was removed, what would happen to the salaries?

A Only Sales department salaries increase

B No salaries change

C All salaries increase by 10%

D Only non-Sales salaries increase

💡 Hint

Refer to key_moments about importance of WHERE clause and execution_table showing selective updates.

Concept Snapshot

UPDATE changes data in rows matching a condition.
Always use WHERE to limit rows updated.
Without WHERE, all rows change.
Check condition carefully to avoid mistakes.
Test UPDATE with SELECT first.

Full Transcript

The UPDATE command changes data in a table. It checks each row against the WHERE condition. If the condition is true, it updates that row; if false, it skips it. This repeats for all rows. Without a WHERE clause, UPDATE changes every row, which can cause big mistakes. In the example, only employees in the Sales department get a 10% salary increase. Rows not in Sales keep their salary. This shows why UPDATE needs caution: to avoid changing unintended rows, always use a correct WHERE condition.