Why constraints matter in SQL - Visual Breakdown

Concept Flow - Why constraints matter

Start: Insert or Update Data

↓

Check Constraints

↓

Pass

↓

Data Saved

When data is added or changed, constraints check if it follows rules. If yes, data saves; if no, error stops it.

Execution Sample

SQL

CREATE TABLE Users (
  ID INT PRIMARY KEY,
  Email VARCHAR(100) UNIQUE NOT NULL
);

INSERT INTO Users VALUES (1, '[e-mail]');
INSERT INTO Users VALUES (2, NULL);

Create a table with rules: ID must be unique, Email must be unique and not empty. Then try adding data.

Execution Table

Step	Action	Data Attempted	Constraint Checked	Result
1	Create Table	Users with ID PK, Email UNIQUE NOT NULL	N/A	Table created
2	Insert	(1, '[e-mail]')	Primary Key, Unique, Not Null	Success: Data saved
3	Insert	(2, NULL)	Not Null on Email	Fail: NULL not allowed, insert rejected

💡 Insert rejected because Email is NULL but NOT NULL constraint requires a value

Variable Tracker

Variable	Start	After Step 2	After Step 3
Users Table Rows	Empty	(1, '[e-mail]')	(1, '[e-mail]')

Key Moments - 2 Insights

Why did the second insert fail even though the ID was unique?

Because the Email column has a NOT NULL constraint, and the second insert tried to put NULL there. See execution_table row 3.

What happens if we try to insert a duplicate ID?

The PRIMARY KEY constraint prevents duplicates, so the insert would fail with an error, similar to the UNIQUE constraint failure shown.

Visual Quiz - 3 Questions

Look at the execution_table, what constraint caused the failure at step 3?

A Not Null constraint

B Unique constraint

C Primary Key constraint

D Foreign Key constraint

💡 Hint

Check the 'Constraint Checked' and 'Result' columns in execution_table row 3

At which step was data successfully saved to the Users table?

A Step 1

B Step 2

C Step 3

D No data saved

💡 Hint

Look at the 'Result' column in execution_table for success messages

If the UNIQUE constraint on Email was removed, what would happen at step 3?

A Insert would succeed despite NULL Email

B Insert would fail due to Primary Key

C Insert would fail due to Not Null constraint

D Insert would fail due to Foreign Key

💡 Hint

NOT NULL constraint is independent of UNIQUE, see execution_table row 3

Concept Snapshot

Constraints are rules on table columns.
They prevent bad or duplicate data.
Common constraints: PRIMARY KEY, UNIQUE, NOT NULL.
If data breaks rules, database rejects it.
This keeps data clean and reliable.

Full Transcript

When you add or change data in a database table, constraints check if the data follows rules. For example, a PRIMARY KEY must be unique, UNIQUE columns cannot repeat values, and NOT NULL columns must have a value. If data breaks these rules, the database stops the change and shows an error. This helps keep the data accurate and trustworthy. In the example, inserting a row with a NULL Email failed because the Email column has a NOT NULL constraint. This shows why constraints matter: they protect your data from mistakes or duplicates.