Date and time types in MySQL - Time & Space Complexity

Time Complexity: Date and time types

O(n)

Understanding Time Complexity

When working with date and time types in MySQL, it's important to understand how operations on these types behave as data grows.

We want to know how the time to process date and time values changes when the amount of data increases.

Scenario Under Consideration

Analyze the time complexity of the following query that filters rows by a date range.

SELECT *
FROM orders
WHERE order_date BETWEEN '2023-01-01' AND '2023-12-31';
    

This query selects all orders placed within the year 2023 by checking the order_date column.

Identify Repeating Operations

Look at what repeats as the query runs:

• Primary operation: Checking each row's order_date to see if it falls in the given range.
• How many times: Once for every row in the orders table.

How Execution Grows With Input

As the number of orders grows, the database checks more dates.

Input Size (n)	Approx. Operations
10	10 date checks
100	100 date checks
1000	1000 date checks

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

Final Time Complexity

Time Complexity: O(n)

This means the time to run the query grows in a straight line as the number of rows increases.

Common Mistake

[X] Wrong: "Date and time checks are instant and don't depend on data size."

[OK] Correct: Each row's date must be checked, so more rows mean more work.

Interview Connect

Understanding how date and time filtering scales helps you explain query performance clearly and confidently.

Self-Check

"What if we add an index on the order_date column? How would the time complexity change?"

Practice

1. Which MySQL data type should you use to store only a date without time?

easy

A. DATE

B. DATETIME

C. TIME

D. TIMESTAMP

Solution

1. Step 1: Understand the data types

   DATE stores only the date (year, month, day). DATETIME and TIMESTAMP store date and time. TIME stores only time.

2. Step 2: Match the requirement

   Since we want to store only the date without time, DATE is the correct choice.

3. Final Answer:

   DATE -> Option A

4. Quick Check:

   Date only = DATE [OK]

Hint: Date only? Use DATE type [OK]

Common Mistakes:

• Choosing DATETIME when only date is needed
• Using TIME for date storage
• Confusing TIMESTAMP with DATE

2. Which of the following is the correct syntax to declare a column named start_time that stores only time in MySQL?

easy

A. start_time TIME;

B. start_time DATE;

C. start_time DATETIME;

D. start_time TIMESTAMP;

Solution

1. Step 1: Identify the correct data type for time only

   The TIME type stores only time values (hours, minutes, seconds).

2. Step 2: Check syntax correctness

   Declaring a column as start_time TIME; is valid syntax in MySQL.

3. Final Answer:

   start_time TIME; -> Option A

4. Quick Check:

   Time only column = TIME type [OK]

Hint: Use TIME type for time-only columns [OK]

Common Mistakes:

• Using DATE or DATETIME for time-only columns
• Missing semicolon in declaration
• Confusing TIMESTAMP with TIME

3. Given the table events with a column event_datetime DATETIME, what will the query SELECT DATE(event_datetime) FROM events WHERE event_datetime = '2024-06-15 14:30:00'; return?

medium

A. 2024-06-15 14:30:00

B. 2024-06-15

C. 14:30:00

D. Error: Invalid function

Solution

1. Step 1: Understand the DATE() function

   The DATE() function extracts only the date part (year-month-day) from a datetime value.

2. Step 2: Apply the function to the given datetime

   Applying DATE('2024-06-15 14:30:00') returns 2024-06-15.

3. Final Answer:

   2024-06-15 -> Option B

4. Quick Check:

   DATE() extracts date only [OK]

Hint: DATE() extracts date part from datetime [OK]

Common Mistakes:

• Expecting full datetime as output
• Confusing DATE() with TIME() function
• Thinking DATE() causes error

4. You wrote this query to insert a time value: INSERT INTO schedule (meeting_time) VALUES ('25:00:00'); but it gives an error. What is the problem?

medium

A. Using DATETIME instead of TIME column type

B. Missing quotes around time value

C. Time value exceeds valid hour range (0-23)

D. Incorrect table name

Solution

1. Step 1: Check the time value format

   Valid time values must have hours between 00 and 23. '25:00:00' has 25 hours, which is invalid.

2. Step 2: Understand MySQL time validation

   MySQL rejects time values outside the valid range, causing an error on insert.

3. Final Answer:

   Time value exceeds valid hour range (0-23) -> Option C

4. Quick Check:

   Hours must be 0-23 in TIME values [OK]

Hint: Hours in TIME must be 0-23 [OK]

Common Mistakes:

• Assuming 25 is valid hour
• Forgetting quotes around time
• Confusing column type with error cause

5. You want to store the exact moment a user logs in, including date and time, and also want automatic timezone conversion to UTC. Which MySQL data type should you use?

hard

A. DATETIME

B. DATE

C. TIME

D. TIMESTAMP

Solution

1. Step 1: Understand the data types and timezone behavior

   TIMESTAMP stores date and time and automatically converts values to UTC for storage and back to local time on retrieval. DATETIME stores date and time but does not handle timezone conversion.

2. Step 2: Match requirement for timezone conversion

   Since automatic timezone conversion is needed, TIMESTAMP is the correct choice.

3. Final Answer:

   TIMESTAMP -> Option D

4. Quick Check:

   TIMESTAMP handles timezone conversion [OK]

Hint: Use TIMESTAMP for timezone-aware datetime [OK]

Common Mistakes:

• Choosing DATETIME and expecting timezone conversion
• Using DATE or TIME for full datetime
• Ignoring timezone needs