FORMAT and LPAD/RPAD in MySQL - Time & Space Complexity

Time Complexity: FORMAT and LPAD/RPAD

O(n)

Understanding Time Complexity

We want to understand how the time it takes to run FORMAT and LPAD/RPAD functions changes as the input size grows.

How does the work these functions do grow when we give them bigger numbers or longer strings?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

SELECT FORMAT(salary, 2) AS formatted_salary,
       LPAD(name, 10, '*') AS padded_name_left,
       RPAD(name, 10, '#') AS padded_name_right
FROM employees;
    

This code formats a number with two decimals and pads names on the left and right to a fixed length.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Applying FORMAT and LPAD/RPAD to each row in the employees table.
• How many times: Once per row, so the number of rows (n) times.

How Execution Grows With Input

Each row requires a fixed amount of work to format and pad, so total work grows as we add more rows.

Input Size (n)	Approx. Operations
10	10 formatting and padding operations
100	100 formatting and padding operations
1000	1000 formatting and padding operations

Pattern observation: The total work 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: "FORMAT and LPAD/RPAD take longer if the strings or numbers are bigger in length."

[OK] Correct: These functions do a fixed amount of work per row, so the main factor is how many rows there are, not the size of each string or number.

Interview Connect

Understanding how simple formatting functions scale helps you explain query performance clearly and shows you can think about how data size affects work done.

Self-Check

"What if we added a nested function inside LPAD that itself loops over the string? How would the time complexity change?"