Column data types (INT, VARCHAR, DATE, DECIMAL) in SQL - Time & Space Complexity

Time Complexity: Column data types (INT, VARCHAR, DATE, DECIMAL)

O(n)

Understanding Time Complexity

When working with column data types like INT, VARCHAR, DATE, and DECIMAL, it's helpful to understand how the choice affects the time it takes to process data.

We want to know how the time to handle data changes as the amount of data grows.

Scenario Under Consideration

Analyze the time complexity of inserting rows with different column data types.

INSERT INTO sales_data (id, product_name, sale_date, price) VALUES
  (1, 'Widget', '2024-01-01', 19.99),
  (2, 'Gadget', '2024-01-02', 29.99),
  (3, 'Thingamajig', '2024-01-03', 9.99);
    

This code inserts multiple rows with columns of types INT, VARCHAR, DATE, and DECIMAL.

Identify Repeating Operations

Look at what repeats as data grows.

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

How Execution Grows With Input

As you add more rows, the database processes each row one by one.

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

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

Final Time Complexity

Time Complexity: O(n)

This means the time to insert data grows in a straight line as you add more rows.

Common Mistake

[X] Wrong: "Using different data types like VARCHAR or DECIMAL makes the insert time grow faster than INT."

[OK] Correct: While data types affect storage size, the main time cost comes from how many rows you insert, not the type itself.

Interview Connect

Understanding how data types relate to time complexity helps you explain database performance clearly and confidently.

Self-Check

"What if we added an index on the product_name column? How would the time complexity of inserts change?"

Practice

1. Which SQL data type is best suited to store a person's full name?

easy

A. DECIMAL

B. INT

C. DATE

D. VARCHAR

Solution

1. Step 1: Understand the data type purpose

   VARCHAR is used to store text or strings, like names.

2. Step 2: Match data type to data

   A person's full name is text, so VARCHAR fits best.

3. Final Answer:

   VARCHAR -> Option D

4. Quick Check:

   Text data = VARCHAR [OK]

Hint: Use VARCHAR for any text data like names or addresses [OK]

Common Mistakes:

• Choosing INT for text
• Using DATE for names
• Using DECIMAL for text

2. Which of the following is the correct way to declare a column for storing a price with two decimal places in SQL?

easy

A. price DATE(10,2)

B. price DECIMAL(10,2)

C. price INT(10,2)

D. price VARCHAR(10,2)

Solution

1. Step 1: Identify the data type for decimal numbers

   DECIMAL is used for numbers with fixed decimal places, like prices.

2. Step 2: Check syntax correctness

   DECIMAL(10,2) means total 10 digits, 2 after decimal point, which is correct.

3. Final Answer:

   price DECIMAL(10,2) -> Option B

4. Quick Check:

   Decimal numbers = DECIMAL(precision, scale) [OK]

Hint: Use DECIMAL(precision, scale) for money or precise decimals [OK]

Common Mistakes:

• Using VARCHAR for numbers
• INT with decimals
• DATE for numeric values

3. Given the table definition:
CREATE TABLE Orders (OrderID INT, OrderDate DATE, CustomerName VARCHAR(50), TotalAmount DECIMAL(8,2));
What will be the result of this insert?
INSERT INTO Orders VALUES (101, '2024-05-10', 'Alice', 123.456);

medium

A. The TotalAmount will store 123.46, rounding to 2 decimals

B. The TotalAmount will store 123.456 exactly

C. The insert will fail due to decimal precision error

D. The TotalAmount will store 123

Solution

1. Step 1: Understand DECIMAL(8,2) behavior

   DECIMAL(8,2) stores numbers with 2 decimal places, rounding if needed.

2. Step 2: Analyze the inserted value 123.456

   Since only 2 decimals allowed, 123.456 rounds to 123.46.

3. Final Answer:

   The TotalAmount will store 123.46, rounding to 2 decimals -> Option A

4. Quick Check:

   DECIMAL rounds to defined decimals [OK]

Hint: DECIMAL rounds extra decimals to defined scale [OK]

Common Mistakes:

• Expecting exact 3 decimals stored
• Thinking insert fails
• Assuming truncation without rounding

4. You have this table creation statement:
CREATE TABLE Employees (ID INT, JoinDate VARCHAR(10));
Why might storing dates as VARCHAR cause problems?

medium

A. Because VARCHAR does not enforce date format, leading to inconsistent data

B. Because INT is better for dates

C. Because VARCHAR cannot store text

D. Because DATE type is slower than VARCHAR

Solution

1. Step 1: Understand VARCHAR vs DATE for dates

   VARCHAR stores text without checking if it is a valid date.

2. Step 2: Identify problems with VARCHAR for dates

   Data can be inconsistent or invalid, causing errors in date operations.

3. Final Answer:

   Because VARCHAR does not enforce date format, leading to inconsistent data -> Option A

4. Quick Check:

   Use DATE type to enforce valid dates [OK]

Hint: Use DATE type to keep dates consistent and valid [OK]

Common Mistakes:

• Thinking INT stores dates
• Believing VARCHAR can't store text
• Assuming DATE is slower

5. You want to create a table to store product details including:
- Product ID as a whole number
- Product name up to 100 characters
- Release date
- Price with up to 7 digits total and 2 decimals

Which is the best SQL column definition for the Price column?

hard

A. Price VARCHAR(7)

B. Price INT

C. Price DECIMAL(7,2)

D. Price DATE

Solution

1. Step 1: Understand the requirements for Price

   Price needs to store numbers with 2 decimal places and up to 7 digits total.

2. Step 2: Match data type to requirements

   DECIMAL(7,2) fits perfectly: 7 digits total, 2 after decimal point.

3. Step 3: Eliminate wrong options

   INT stores whole numbers only, VARCHAR stores text, DATE is for dates.

4. Final Answer:

   Price DECIMAL(7,2) -> Option C

5. Quick Check:

   Use DECIMAL for precise decimal numbers [OK]

Hint: Use DECIMAL(total_digits, decimals) for prices [OK]

Common Mistakes:

• Using INT for prices with decimals
• Using VARCHAR for numbers
• Confusing DATE with price