Column definitions and constraints in MySQL - Time & Space Complexity

Time Complexity: Column definitions and constraints

O(log n)

Understanding Time Complexity

When we create or change a table, we define columns and rules for data. Understanding how this affects time helps us know how fast the database works when adding or checking data.

We want to see how the time to add or check data grows as the table gets bigger.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

CREATE TABLE Users (
  id INT PRIMARY KEY,
  username VARCHAR(50) UNIQUE,
  email VARCHAR(100) NOT NULL,
  age INT CHECK (age >= 18)
);

INSERT INTO Users (id, username, email, age) VALUES (1, 'alice', '[e-mail]', 25);
    

This code creates a table with rules for each column and inserts one row, checking those rules.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Checking constraints like uniqueness and validity when inserting data.
• How many times: For each insert, the database performs index lookups to check PRIMARY KEY and UNIQUE constraints (O(log n) time).

How Execution Grows With Input

As the table grows, checking constraints like UNIQUE or PRIMARY KEY takes more time because the database must ensure no duplicates.

Input Size (n)	Approx. Operations
10	About 3 checks
100	About 7 checks
1000	About 10 checks

Pattern observation: The number of checks grows logarithmically with the number of rows.

Final Time Complexity

Time Complexity: O(log n)

This means the time to check constraints grows logarithmically as the table gets bigger.

Common Mistake

[X] Wrong: "Checking constraints always takes the same time no matter how big the table is."

[OK] Correct: The database often needs to search indexes over existing data to ensure rules are followed, so more data means more work.

Interview Connect

Knowing how constraints affect time helps you explain database behavior clearly. It shows you understand how data rules impact performance in real projects.

Self-Check

"What if we added an index on the username column? How would the time complexity change when checking uniqueness?"

Practice

1. Which constraint ensures that a column cannot have empty (NULL) values in MySQL?

easy

A. NOT NULL

B. UNIQUE

C. PRIMARY KEY

D. DEFAULT

Solution

1. Step 1: Understand the purpose of NOT NULL

   The NOT NULL constraint prevents a column from having NULL values, meaning it must always have data.

2. Step 2: Compare with other constraints

   UNIQUE allows NULLs but no duplicates, PRIMARY KEY implies NOT NULL and uniqueness, and DEFAULT sets a default value but does not prevent NULL.

3. Final Answer:

   NOT NULL -> Option A

4. Quick Check:

   Prevent empty values = NOT NULL [OK]

Hint: NOT NULL means no empty values allowed [OK]

Common Mistakes:

• Confusing UNIQUE with NOT NULL
• Thinking DEFAULT prevents NULL
• Assuming PRIMARY KEY is only for uniqueness

2. Which of the following is the correct way to define a column named id as an auto-incrementing primary key in MySQL?

easy

A. id AUTO_INCREMENT INT PRIMARY KEY

B. id INT AUTO_INCREMENT PRIMARY

C. id INT PRIMARY KEY AUTO_INCREMENT

D. id PRIMARY KEY INT AUTO_INCREMENT

Solution

1. Step 1: Recall correct column definition order

   In MySQL, the correct syntax places the data type first, then constraints like PRIMARY KEY and AUTO_INCREMENT.

2. Step 2: Validate each option's syntax

   id INT PRIMARY KEY AUTO_INCREMENT follows the correct order: id INT PRIMARY KEY AUTO_INCREMENT. Others have incorrect order or missing keywords.

3. Final Answer:

   id INT PRIMARY KEY AUTO_INCREMENT -> Option C

4. Quick Check:

   Data type first, then constraints [OK]

Hint: Data type first, then PRIMARY KEY and AUTO_INCREMENT [OK]

Common Mistakes:

• Placing AUTO_INCREMENT before data type
• Using PRIMARY instead of PRIMARY KEY
• Mixing order of keywords

3. Given the table definition:

CREATE TABLE users (
  user_id INT PRIMARY KEY,
  email VARCHAR(100) UNIQUE NOT NULL,
  age INT DEFAULT 18
);

What will happen if you try to insert:

INSERT INTO users (user_id, email) VALUES (1, NULL);

medium

A. Insert fails due to NOT NULL constraint on email

B. Insert succeeds with email set to NULL

C. Insert succeeds with email set to default value

D. Insert fails due to UNIQUE constraint violation

Solution

1. Step 1: Check the email column constraints

   Email is defined as UNIQUE NOT NULL, so it cannot be NULL.

2. Step 2: Analyze the insert statement

   The insert tries to set email to NULL, violating the NOT NULL constraint, causing an error.

3. Final Answer:

   Insert fails due to NOT NULL constraint on email -> Option A

4. Quick Check:

   NOT NULL rejects NULL values [OK]

Hint: NOT NULL columns reject NULL inserts [OK]

Common Mistakes:

• Assuming DEFAULT applies when value is NULL
• Confusing UNIQUE with NOT NULL
• Thinking NULL is allowed if UNIQUE

4. Consider this table creation statement:

CREATE TABLE products (
  product_id INT PRIMARY KEY,
  name VARCHAR(50) UNIQUE,
  price DECIMAL(5,2) NOT NULL DEFAULT 0.00
);

Which of the following statements will cause an error?

medium

A. INSERT INTO products (product_id, name, price) VALUES (1, 'Pen', 1.50);

B. INSERT INTO products (product_id, name) VALUES (2, 'Book');

C. INSERT INTO products (product_id, price) VALUES (3, 2.00);

D. INSERT INTO products (product_id, name, price) VALUES (1, 'Pencil', 0.50);

Solution

1. Step 1: Check constraints on each insert

   INSERT INTO products (product_id, name, price) VALUES (1, 'Pen', 1.50); inserts all required fields correctly. INSERT INTO products (product_id, name) VALUES (2, 'Book'); omits price but uses default 0.00, allowed. INSERT INTO products (product_id, price) VALUES (3, 2.00); omits name, which is nullable, allowed.

2. Step 2: Identify duplicate primary key error

   INSERT INTO products (product_id, name, price) VALUES (1, 'Pencil', 0.50); tries to insert product_id 1 again, violating the PRIMARY KEY uniqueness constraint, causing an error.

3. Final Answer:

   INSERT INTO products (product_id, name, price) VALUES (1, 'Pencil', 0.50); -> Option D

4. Quick Check:

   PRIMARY KEY must be unique [OK]

Hint: Duplicate PRIMARY KEY values cause errors [OK]

Common Mistakes:

• Assuming UNIQUE allows duplicates
• Forgetting DEFAULT applies only if column omitted
• Ignoring PRIMARY KEY uniqueness

5. You want to create a table orders where order_id is a primary key, customer_email must be unique and not null, and order_date defaults to the current date if not provided. Which of the following column definitions is correct?

hard

A. order_id INT PRIMARY KEY, customer_email VARCHAR(100) NOT NULL UNIQUE, order_date DATE DEFAULT NOW()

B. order_id INT PRIMARY KEY, customer_email VARCHAR(100) UNIQUE NOT NULL, order_date DATE DEFAULT CURRENT_DATE

C. order_id INT PRIMARY KEY, customer_email VARCHAR(100) UNIQUE, order_date DATE DEFAULT CURRENT_TIMESTAMP

D. order_id INT PRIMARY KEY, customer_email VARCHAR(100) NOT NULL UNIQUE, order_date DATE DEFAULT CURDATE()

Solution

1. Step 1: Check constraints on customer_email

   The column must be both UNIQUE and NOT NULL. Using either UNIQUE NOT NULL or NOT NULL UNIQUE is valid in MySQL.

2. Step 2: Verify default for order_date

   MySQL supports DEFAULT CURRENT_DATE for DATE columns. NOW() and CURRENT_TIMESTAMP return datetime, not date, causing errors. CURDATE() is a function and cannot be used directly as default.

3. Step 3: Confirm full correctness

   order_id INT PRIMARY KEY, customer_email VARCHAR(100) UNIQUE NOT NULL, order_date DATE DEFAULT CURRENT_DATE uses correct syntax for all constraints and default value.

4. Final Answer:

   order_id INT PRIMARY KEY, customer_email VARCHAR(100) UNIQUE NOT NULL, order_date DATE DEFAULT CURRENT_DATE -> Option B

5. Quick Check:

   Use CURRENT_DATE for DATE default [OK]

Hint: Use CURRENT_DATE for DATE default, UNIQUE NOT NULL order matters [OK]

Common Mistakes:

• Using NOW() or CURRENT_TIMESTAMP for DATE default
• Trying to use functions like CURDATE() as default
• Confusing UNIQUE and NOT NULL order