DEFAULT values in SQL - Time & Space Complexity

Time Complexity: DEFAULT values

O(n)

Understanding Time Complexity

We want to understand how using DEFAULT values in SQL affects the time it takes to insert data.

Specifically, does setting default values change how long the database works as data grows?

Scenario Under Consideration

Analyze the time complexity of inserting rows with DEFAULT values.

INSERT INTO orders (order_id, order_date, status) 
VALUES (1, DEFAULT, DEFAULT);

INSERT INTO orders (order_id, order_date, status) 
VALUES (2, '2024-06-01', DEFAULT);

INSERT INTO orders (order_id, order_date, status) 
VALUES (3, DEFAULT, 'shipped');
    

This code inserts rows using DEFAULT for some columns when no explicit value is given.

Identify Repeating Operations

Look at what repeats when inserting many rows with DEFAULT values.

• Primary operation: Inserting each row into the table.
• How many times: Once per row inserted.

How Execution Grows With Input

Each new row added means one more insert operation.

Input Size (n)	Approx. Operations
10	10 insert operations
100	100 insert operations
1000	1000 insert operations

Pattern observation: The work grows directly with the number of rows inserted.

Final Time Complexity

Time Complexity: O(n)

This means the time to insert rows grows in a straight line as you add more rows, regardless of using DEFAULT values.

Common Mistake

[X] Wrong: "Using DEFAULT values makes inserts faster because the database skips work."

[OK] Correct: The database still processes each row and applies defaults internally, so the time grows with the number of rows just like normal inserts.

Interview Connect

Understanding how default values affect insert time shows you know how databases handle data efficiently, a useful skill in real projects and interviews.

Self-Check

"What if we inserted rows in bulk without specifying columns that have DEFAULT values? How would that affect the time complexity?"

Practice

1. What does the DEFAULT keyword do in a SQL table column definition?

easy

A. Deletes the column if no value is provided

B. Prevents any value from being inserted into the column

C. Sets a value automatically if no value is provided during insert

D. Requires the user to always provide a value

Solution

1. Step 1: Understand the purpose of DEFAULT

   The DEFAULT keyword assigns a preset value to a column when no value is given during data insertion.

2. Step 2: Compare options with this purpose

   Only Sets a value automatically if no value is provided during insert correctly describes this automatic assignment behavior.

3. Final Answer:

   Sets a value automatically if no value is provided during insert -> Option C

4. Quick Check:

   DEFAULT = automatic value assignment [OK]

Hint: DEFAULT fills missing values automatically [OK]

Common Mistakes:

• Thinking DEFAULT deletes or restricts data
• Confusing DEFAULT with NOT NULL constraint
• Assuming DEFAULT requires manual input

2. Which of the following is the correct syntax to set a default value of 100 for a column named score in a table?

easy

A. score INT DEFAULT 100

B. score INT SET DEFAULT 100

C. score INT DEFAULT = 100

D. score INT DEFAULT TO 100

Solution

1. Step 1: Recall standard SQL syntax for DEFAULT

   The correct syntax is: column_name data_type DEFAULT value, without extra keywords or symbols.

2. Step 2: Check each option

   score INT DEFAULT 100 matches the correct syntax exactly. Options B, C, and D add incorrect keywords or symbols.

3. Final Answer:

   score INT DEFAULT 100 -> Option A

4. Quick Check:

   DEFAULT syntax = column type DEFAULT value [OK]

Hint: DEFAULT syntax: column type DEFAULT value [OK]

Common Mistakes:

• Adding extra keywords like SET or TO
• Using equals sign (=) after DEFAULT
• Placing DEFAULT before data type

3. Given the table users with column status VARCHAR(10) DEFAULT 'active', what will be the result of this query?

INSERT INTO users (id, name) VALUES (1, 'Alice');
SELECT id, name, status FROM users WHERE id = 1;

medium

A. [1, 'Alice', NULL]

B. [1, 'Alice', 'active']

C. [1, 'Alice', 'inactive']

D. Syntax error

Solution

1. Step 1: Understand DEFAULT behavior on insert

   Since status has a default of 'active' and no value was provided, SQL inserts 'active' automatically.

2. Step 2: Check the SELECT output

   The SELECT query will show id=1, name='Alice', and status='active' as inserted or defaulted.

3. Final Answer:

   [1, 'Alice', 'active'] -> Option B

4. Quick Check:

   DEFAULT fills missing column with 'active' [OK]

Hint: Missing column uses DEFAULT value automatically [OK]

Common Mistakes:

• Assuming missing columns get NULL instead of DEFAULT
• Thinking query causes syntax error
• Confusing default value with another string

4. Consider this table creation statement:

CREATE TABLE orders (
  id INT PRIMARY KEY,
  quantity INT DEFAULT 1,
  price DECIMAL(5,2) DEFAULT 0.00
);

Which of the following INSERT statements will cause an error?

medium

A. INSERT INTO orders (id, price) VALUES (12, 'free');

B. INSERT INTO orders (id, quantity) VALUES (11, DEFAULT);

C. INSERT INTO orders (id) VALUES (10);

D. INSERT INTO orders (id, quantity, price) VALUES (13, 5, 9.99);

Solution

1. Step 1: Analyze each INSERT statement

   INSERT INTO orders (id) VALUES (10); inserts id only; quantity and price get defaults (valid). INSERT INTO orders (id, quantity) VALUES (11, DEFAULT); uses DEFAULT keyword explicitly (valid). INSERT INTO orders (id, price) VALUES (12, 'free'); tries to insert 'free' into price (decimal), causing type error. INSERT INTO orders (id, quantity, price) VALUES (13, 5, 9.99); provides all valid values.

2. Step 2: Identify the error

   Only INSERT INTO orders (id, price) VALUES (12, 'free'); has a data type mismatch causing an error.

3. Final Answer:

   INSERT INTO orders (id, price) VALUES (12, 'free'); -> Option A

4. Quick Check:

   Wrong data type in INSERT causes error [OK]

Hint: Check data types when inserting values [OK]

Common Mistakes:

• Assuming DEFAULT keyword is invalid in VALUES
• Ignoring data type mismatch errors
• Thinking missing columns cause errors

5. You have a table products with columns id INT, name VARCHAR(50), and stock INT DEFAULT 0. You want to insert multiple rows but only specify id and name. Which SQL statement correctly inserts two products using DEFAULT for stock?

hard

A. INSERT INTO products (id, name, stock) VALUES (1, 'Pen', 0), (2, 'Pencil', 0);

B. INSERT INTO products VALUES (1, 'Pen'), (2, 'Pencil');

C. INSERT INTO products (id, name, stock) VALUES (1, 'Pen', DEFAULT), (2, 'Pencil', DEFAULT);

D. INSERT INTO products (id, name) VALUES (1, 'Pen'), (2, 'Pencil');

Solution

1. Step 1: Understand requirement for column specification

   To only specify id and name, list only those columns; omitted columns like stock use their DEFAULT value automatically.

2. Step 2: Evaluate each option

   INSERT INTO products (id, name) VALUES (1, 'Pen'), (2, 'Pencil'); specifies only id and name, stock uses DEFAULT (correct).
   INSERT INTO products VALUES (1, 'Pen'), (2, 'Pencil'); no column list with 2 values (vs 3 columns) causes mismatch error.
   INSERT INTO products (id, name, stock) VALUES (1, 'Pen', DEFAULT), (2, 'Pencil', DEFAULT); specifies stock column (violates 'only id and name').
   INSERT INTO products (id, name, stock) VALUES (1, 'Pen', 0), (2, 'Pencil', 0); specifies stock explicitly with value (not relying on DEFAULT).

3. Final Answer:

   INSERT INTO products (id, name) VALUES (1, 'Pen'), (2, 'Pencil'); -> Option D

4. Quick Check:

   Omit column with DEFAULT = auto-use [OK]

Hint: Omit columns with DEFAULT to use them automatically [OK]

Common Mistakes:

• No column list + fewer values = mismatch error
• Including stock column even with DEFAULT keyword
• Hardcoding default value instead of omitting column