Why Column data types (INT, VARCHAR, DATE, DECIMAL) in SQL? - Purpose & Use Cases

The Big Idea

What if your data could organize itself perfectly and never get mixed up?

The Scenario

Imagine you have a huge notebook where you write down all your friends' information: their age, names, birthdays, and how much money they owe you. You just scribble everything without any order or rules.

The Problem

Without rules, your notebook becomes messy. You might write a name as a number or a birthday as random letters. It's hard to find or trust the info, and mistakes happen often.

The Solution

Using column data types is like giving each notebook column a clear label and rule: ages must be numbers, names must be words, birthdays must be dates, and money must have decimals. This keeps your data neat, correct, and easy to use.

Before vs After

✗ Before

CREATE TABLE friends (age, name, birthday, debt);

✓ After

CREATE TABLE friends (age INT, name VARCHAR(50), birthday DATE, debt DECIMAL(10,2));

What It Enables

It lets databases store and check data correctly, making searching, sorting, and calculating fast and reliable.

Real Life Example

A store uses data types to keep track of product prices (DECIMAL), product names (VARCHAR), stock counts (INT), and expiration dates (DATE) so everything is accurate and easy to manage.

Key Takeaways

Data types give clear rules for each kind of data.

They prevent errors by ensuring data fits the right format.

This makes data easy to organize, search, and calculate.

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