Why NOT NULL and DEFAULT constraints in MySQL? - Purpose & Use Cases

The Big Idea

What if your database could stop you from making costly data mistakes before they happen?

The Scenario

Imagine you are keeping a paper list of your friends' contact details. Sometimes you forget to write down their phone number or leave the space blank. Later, when you want to call them, you realize some numbers are missing or unclear.

The Problem

Manually checking every entry to make sure no phone number is missing is slow and tiring. You might accidentally miss some blanks or write wrong numbers. This causes confusion and wastes time when you need the info quickly.

The Solution

Using NOT NULL and DEFAULT constraints in a database is like having a rule that says "You must always write a phone number" and "If you forget, write this default number instead." This keeps your data complete and consistent automatically.

Before vs After

✗ Before

INSERT INTO friends (name, phone) VALUES ('Alice', NULL);

✓ After

CREATE TABLE friends (name VARCHAR(50), phone VARCHAR(20) NOT NULL DEFAULT '000-000-0000');

What It Enables

This lets you trust your data is always complete and ready to use without extra checking or fixing.

Real Life Example

A company database where every employee must have an email address recorded. Using NOT NULL ensures no employee record is missing this important contact info, and DEFAULT can fill in a placeholder if needed.

Key Takeaways

NOT NULL ensures important data is never left empty.

DEFAULT provides a fallback value when no data is given.

Together, they keep your database clean and reliable.