Data type planning in No-Code - Time & Space Complexity

Time Complexity: Data type planning

O(n)

Understanding Time Complexity

When planning data types, it is important to understand how the choice affects the speed of operations.

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

Scenario Under Consideration

Analyze the time complexity of choosing and using data types for storing and accessing data.

# Example: Using a list to store numbers
numbers = []
for i in range(n):
    numbers.append(i)

# Accessing an element
value = numbers[k]
    

This code stores numbers in a list and accesses one element by its position.

Identify Repeating Operations

Look for repeated actions that take time as data grows.

• Primary operation: Adding items to the list one by one.
• How many times: Exactly n times, once for each item.

How Execution Grows With Input

As the number of items increases, the time to add all items grows in a straight line.

Input Size (n)	Approx. Operations
10	10 additions
100	100 additions
1000	1000 additions

Pattern observation: Doubling the input doubles the work needed.

Final Time Complexity

Time Complexity: O(n)

This means the time to add items grows directly with the number of items.

Common Mistake

[X] Wrong: "Accessing any item in the list takes longer as the list grows."

[OK] Correct: Access by position in a list is very fast and does not slow down with more items.

Interview Connect

Understanding how data types affect operation speed helps you choose the right tool for the job, a skill valued in many real-world tasks.

Self-Check

"What if we used a different data type like a linked list instead of a list? How would the time complexity for accessing an element change?"

Practice

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

easy

A. Date

B. Text

C. Boolean

D. Number

Solution

1. Step 1: Understand the nature of the data

   A person's full name consists of letters and possibly spaces, which is textual information.

2. Step 2: Match data type to data nature

   Text data type is designed to store words and characters, making it the best fit.

3. Final Answer:

   Text -> Option B

4. Quick Check:

   Names are words, so use Text [OK]

Hint: Names are words, so always choose Text type [OK]

Common Mistakes:

• Choosing Number for names
• Using Boolean for text data
• Selecting Date for names

2. Which of the following is the correct data type to store a true/false value?

easy

A. Boolean

B. Number

C. Date

D. Text

Solution

1. Step 1: Identify the data type for true/false values

   true/false values represent two states, which is exactly what Boolean data type stores.

2. Step 2: Confirm Boolean is the correct choice

   Boolean type holds only true or false, making it the best fit for such data.

3. Final Answer:

   Boolean -> Option A

4. Quick Check:

   true/false = Boolean [OK]

Hint: true or false means Boolean type [OK]

Common Mistakes:

• Using Text for true/false
• Choosing Number for Boolean values
• Selecting Date for true/false

3. If you want to store a person's birthdate, which data type should you choose?

medium

A. Boolean

B. Text

C. Number

D. Date

Solution

1. Step 1: Understand the data to be stored

   A birthdate is a specific point in time, including day, month, and year.

2. Step 2: Select the data type that handles dates

   Date data type is designed to store calendar dates accurately.

3. Final Answer:

   Date -> Option D

4. Quick Check:

   Birthdate = Date type [OK]

Hint: Dates need Date type, not Text or Number [OK]

Common Mistakes:

• Using Text for dates
• Choosing Number for dates
• Selecting Boolean for dates

4. A database field is set to Number type but you try to enter the text 'Hello'. What will likely happen?

medium

A. The text 'Hello' will be stored without error

B. The system will convert 'Hello' to a number automatically

C. An error or rejection will occur because of wrong data type

D. The field will store 'Hello' as Boolean true

Solution

1. Step 1: Understand data type restrictions

   Number type fields accept only numeric values, not text.

2. Step 2: Predict system behavior on wrong input

   Entering text in a Number field causes an error or rejection to keep data clean.

3. Final Answer:

   An error or rejection will occur because of wrong data type -> Option C

4. Quick Check:

   Text in Number field causes error [OK]

Hint: Text in Number field causes error, not auto-conversion [OK]

Common Mistakes:

• Assuming automatic conversion of text to number
• Thinking text stores as Boolean
• Believing text stores without error

5. You need to plan data types for a contact list with fields: Name, Phone Number, Email, Is Favorite, and Last Contact Date. Which is the best data type plan?

hard

A. Name: Text, Phone Number: Text, Email: Text, Is Favorite: Boolean, Last Contact Date: Text

B. Name: Text, Phone Number: Number, Email: Text, Is Favorite: Boolean, Last Contact Date: Date

C. Name: Text, Phone Number: Text, Email: Number, Is Favorite: Text, Last Contact Date: Date

D. Name: Number, Phone Number: Text, Email: Text, Is Favorite: Boolean, Last Contact Date: Date

Solution

1. Step 1: Assign correct types to each field

   Name is words, so Text; Phone Number is digits but often stored as Text to keep formatting; Email is text; Is Favorite is true/false, so Boolean; Last Contact Date is a date.

2. Step 2: Evaluate each option

   Name: Text, Phone Number: Text (to preserve formatting and leading zeros), Email: Text, Is Favorite: Boolean, Last Contact Date: Date is the best match. Name: Text, Phone Number: Text, Email: Text, Is Favorite: Boolean, Last Contact Date: Text correctly assigns these types except Last Contact Date is Text, which is not ideal.

3. Step 3: Review other options

   Name: Text, Phone Number: Number, Email: Text, Is Favorite: Boolean, Last Contact Date: Date uses Number for Phone Number, which can cause issues with formatting and leading zeros. Name: Text, Phone Number: Text, Email: Text, Is Favorite: Boolean, Last Contact Date: Text uses Text for Last Contact Date, which is less ideal than Date type.

4. Final Answer:

   Name: Text, Phone Number: Text, Email: Text, Is Favorite: Boolean, Last Contact Date: Date -> Option A is incorrect as Last Contact Date is Text, so the best correct plan is Name: Text, Phone Number: Number, Email: Text, Is Favorite: Boolean, Last Contact Date: Date.

5. Quick Check:

   Phone numbers are better stored as Text; dates should use Date type [Fix applied]

Hint: Match each field to its natural data type [OK]

Common Mistakes:

• Using Number for Name
• Using Text for Boolean fields
• Using Number for Email