Column types and constraints in Flask - Performance & Optimization

Performance: Column types and constraints

MEDIUM IMPACT

This affects the database query speed and the initial page load time when fetching data through Flask.

Defining database columns for a Flask app model

Flask

class User(db.Model):
    id = db.Column(db.Integer, primary_key=True)
    age = db.Column(db.Integer, nullable=False)
    email = db.Column(db.String(120), unique=True, nullable=False)

Using correct data types and constraints reduces data size and speeds up database operations.

📈 Performance GainFaster queries and smaller data payloads improve LCP and reduce server load.

Defining database columns for a Flask app model

Flask

class User(db.Model):
    id = db.Column(db.String(255), primary_key=True)
    age = db.Column(db.String(255))
    email = db.Column(db.String(255), unique=False, nullable=True)

Using large string types for numeric data and missing constraints causes larger data storage and slower queries.

📉 Performance CostIncreases query time and data transfer size, impacting LCP negatively.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Using large string types for numeric data	N/A	N/A	Increases server response time	[X] Bad
Using correct data types and constraints	N/A	N/A	Reduces server response time	[OK] Good

Rendering Pipeline

Column types and constraints affect how quickly the database can return data, which impacts the server response time and thus the browser's ability to render content.

→Server Processing

→Network Transfer

→Rendering

⚠️ BottleneckServer Processing due to inefficient queries or large data payloads

Core Web Vital Affected

LCP

This affects the database query speed and the initial page load time when fetching data through Flask.

Optimization Tips

1Use the smallest appropriate column type for your data.

2Add constraints like unique and nullable to help the database optimize.

3Avoid using large string types for numeric or fixed-size data.

Performance Quiz - 3 Questions

How does using an inappropriate column type like String for numeric data affect performance?

A It increases data size and slows down queries.

B It makes queries faster.

C It has no effect on performance.

D It reduces server load.

DevTools: Network

How to check: Open DevTools, go to Network tab, reload the page, and inspect the time taken for API/database calls.

What to look for: Look for long server response times indicating slow database queries due to inefficient column types or constraints.

Practice

1. Which SQLAlchemy column type should you use in Flask to store text data of variable length?

easy

A. db.String

B. db.Integer

C. db.Boolean

D. db.DateTime

Solution

1. Step 1: Understand column types for text data

   Text data of variable length is best stored using a string type that allows flexible length.

2. Step 2: Match the correct SQLAlchemy type

   db.String is designed for variable-length text, unlike db.Integer or db.Boolean.

3. Final Answer:

   db.String -> Option A

4. Quick Check:

   Variable-length text = db.String [OK]

Hint: Text data uses db.String type in Flask models [OK]

Common Mistakes:

• Choosing db.Integer for text data
• Using db.Boolean for strings
• Confusing db.DateTime with text types

2. Which of the following is the correct way to declare a non-nullable integer column named age in a Flask model?

easy

A. age = db.Column(db.Integer, nullable=True)

B. age = db.Column(db.Boolean, nullable=False)

C. age = db.Column(db.String, nullable=False)

D. age = db.Column(db.Integer, nullable=False)

Solution

1. Step 1: Identify the correct type for age

   Age should be stored as an integer, so db.Integer is correct.

2. Step 2: Set the nullable constraint

   To make the column non-nullable, use nullable=False.

3. Final Answer:

   age = db.Column(db.Integer, nullable=False) -> Option D

4. Quick Check:

   Integer + non-nullable = age = db.Column(db.Integer, nullable=False) [OK]

Hint: Use nullable=False to prevent empty values [OK]

Common Mistakes:

• Setting nullable=True when non-null is needed
• Using wrong data type like String for age
• Confusing Boolean with Integer type

3. Given this Flask model column declaration:

email = db.Column(db.String(120), unique=True, nullable=False)

What does the unique=True constraint do?

medium

A. Prevents duplicate email values in the table

B. Makes the email column optional

C. Allows multiple rows to have the same email

D. Automatically converts emails to lowercase

Solution

1. Step 1: Understand the unique constraint

   The unique=True constraint ensures no two rows have the same value in this column.

2. Step 2: Apply this to the email column

   This means duplicate emails are not allowed, keeping each email distinct.

3. Final Answer:

   Prevents duplicate email values in the table -> Option A

4. Quick Check:

   unique=True means no duplicates [OK]

Hint: unique=True means no two rows share the same value [OK]

Common Mistakes:

• Thinking unique=True allows duplicates
• Confusing unique with nullable
• Assuming unique changes data format

4. What is wrong with this Flask model column declaration?

price = db.Column(db.String, nullable=False, unique='yes')

medium

A. The nullable argument cannot be used with unique

B. The unique argument should be a boolean, not a string

C. The column type db.String cannot be used for price

D. The column name price is a reserved keyword

Solution

1. Step 1: Check the unique argument type

   The unique parameter expects a boolean value (True or False), not a string.

2. Step 2: Identify the error in the code

   Passing unique='yes' is invalid and will cause an error.

3. Final Answer:

   The unique argument should be a boolean, not a string -> Option B

4. Quick Check:

   unique must be True or False, not 'yes' [OK]

Hint: unique must be True/False, never a string [OK]

Common Mistakes:

• Using string values for boolean parameters
• Thinking nullable and unique conflict
• Assuming price is reserved keyword

5. You want to create a Flask model column for a user's phone number that must be exactly 10 digits, unique, and cannot be empty. Which declaration is best?

hard

A. phone = db.Column(db.String, unique=False, nullable=False)

B. phone = db.Column(db.Integer, unique=True, nullable=False)

C. phone = db.Column(db.String(10), unique=True, nullable=False)

D. phone = db.Column(db.String(15), nullable=True)

Solution

1. Step 1: Choose the correct type for phone numbers

   Phone numbers often contain leading zeros, so db.String(10) is better than db.Integer.

2. Step 2: Apply constraints for uniqueness and non-null

   Use unique=True to prevent duplicates and nullable=False to disallow empty values.

3. Final Answer:

   phone = db.Column(db.String(10), unique=True, nullable=False) -> Option C

4. Quick Check:

   String(10) + unique + non-null = phone = db.Column(db.String(10), unique=True, nullable=False) [OK]

Hint: Use String with length, unique=True, nullable=False for fixed phone numbers [OK]

Common Mistakes:

• Using Integer type losing leading zeros
• Allowing nullable=True when value is required
• Ignoring unique constraint for phone numbers