Why ORM simplifies database access in Flask - Performance Evidence

Performance: Why ORM simplifies database access

MEDIUM IMPACT

This concept affects the speed of database queries and the efficiency of data handling in the app, impacting how fast pages load and respond.

Accessing and manipulating database records in a Flask app

Flask

user = User.query.get(user_id)
# Using Flask-SQLAlchemy ORM to fetch user by id

ORM abstracts SQL, reduces errors, and can optimize queries internally, improving database access speed.

📈 Performance GainFewer redundant queries and better caching, leading to faster response and improved INP

Accessing and manipulating database records in a Flask app

Flask

cursor.execute('SELECT * FROM users WHERE id = %s', (user_id,))
user = cursor.fetchone()
# Manual SQL queries everywhere

Manual SQL queries can be error-prone, cause inconsistent query patterns, and lead to inefficient database access.

📉 Performance CostCan cause multiple redundant queries and slow response times due to lack of query optimization

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Manual SQL queries with repeated calls	N/A	N/A	N/A	[X] Bad
ORM with optimized queries and caching	N/A	N/A	N/A	[OK] Good

Rendering Pipeline

ORM usage affects the backend data fetching stage before rendering. Efficient ORM queries reduce backend processing time, speeding up data delivery to the frontend.

→Backend Data Fetching

→Network Transfer

→Rendering

⚠️ BottleneckBackend Data Fetching (database query execution)

Core Web Vital Affected

INP

This concept affects the speed of database queries and the efficiency of data handling in the app, impacting how fast pages load and respond.

Optimization Tips

1Use ORM to avoid manual SQL errors and improve query consistency.

2Leverage ORM features like lazy loading and caching to reduce database calls.

3Monitor database query count and duration to ensure ORM optimizations are effective.

Performance Quiz - 3 Questions

How does using an ORM typically improve database access performance in a Flask app?

A By increasing the number of raw SQL queries sent to the database

B By adding extra layers that slow down data retrieval

C By reducing manual query errors and optimizing query patterns

D By forcing all queries to be synchronous

DevTools: Network

How to check: Open DevTools, go to Network tab, filter by XHR or fetch, and observe the number and duration of database API calls.

What to look for: Look for fewer, faster API calls indicating efficient database access; many slow calls suggest poor query patterns.

Practice

1. Why does using an ORM in Flask make working with databases easier?

easy

A. Because it only works with one type of database

B. Because it requires writing more SQL code manually

C. Because it lets you use Python objects instead of writing SQL queries directly

D. Because it removes the need to understand databases at all

Solution

1. Step 1: Understand ORM purpose

   ORM stands for Object-Relational Mapping, which connects Python classes to database tables.

2. Step 2: Identify how ORM simplifies work

   It lets you use Python objects to create, read, update, and delete data without writing SQL queries manually.

3. Final Answer:

   Because it lets you use Python objects instead of writing SQL queries directly -> Option C

4. Quick Check:

   ORM uses Python objects, not raw SQL [OK]

Hint: Think: ORM means Python objects replace SQL queries [OK]

Common Mistakes:

• Thinking ORM requires more SQL code
• Believing ORM only supports one database
• Assuming ORM removes all database knowledge needs

2. Which of the following is the correct way to define a model class using Flask's ORM (SQLAlchemy)?

easy

A. class User: id = Column(Integer, primary_key=True)

B. def User(): id = Column(Integer, primary_key=True)

C. User = db.Model(id = Column(Integer, primary_key=True))

D. class User(db.Model): id = db.Column(db.Integer, primary_key=True)

Solution

1. Step 1: Recall Flask SQLAlchemy model syntax

   Models inherit from db.Model and define columns with db.Column and types like db.Integer.

2. Step 2: Check each option

   class User(db.Model): id = db.Column(db.Integer, primary_key=True) correctly defines a class inheriting db.Model with a column using db.Column and db.Integer.

3. Final Answer:

   class User(db.Model): id = db.Column(db.Integer, primary_key=True) -> Option D

4. Quick Check:

   Model class inherits db.Model and uses db.Column [OK]

Hint: Model classes inherit db.Model and use db.Column for fields [OK]

Common Mistakes:

• Not inheriting from db.Model
• Using Column without db prefix
• Defining model as a function instead of class

3. Given this Flask ORM code:

user = User(name='Alice')
db.session.add(user)
db.session.commit()
print(user.id)

What will print(user.id) output after commit?

medium

A. The new unique ID assigned by the database

B. None

C. An error because id is not set

D. The string 'Alice'

Solution

1. Step 1: Understand ORM session commit behavior

   When you add and commit a new object, the database assigns a unique ID (primary key) automatically.

2. Step 2: Check what user.id holds after commit

   After commit, ORM updates the object with the assigned ID, so user.id contains that new value.

3. Final Answer:

   The new unique ID assigned by the database -> Option A

4. Quick Check:

   Commit assigns and updates object ID [OK]

Hint: After commit, ORM sets the object's ID from the database [OK]

Common Mistakes:

• Expecting id to be None before commit
• Thinking id is the name value
• Assuming commit does not update object fields

4. What is wrong with this Flask ORM code snippet?

user = User(name='Bob')
db.session.add(user)
print(user.id)

medium

A. It will print None because commit is missing

B. It will raise a syntax error

C. It will print the name instead of id

D. It will print a random number

Solution

1. Step 1: Identify missing commit

   The code adds the user to the session but does not commit, so the database does not assign an ID yet.

2. Step 2: Understand user.id value before commit

   Before commit, user.id is None because the database has not generated the primary key.

3. Final Answer:

   It will print None because commit is missing -> Option A

4. Quick Check:

   Commit needed to assign ID [OK]

Hint: Remember to commit to get database-generated IDs [OK]

Common Mistakes:

• Forgetting to call commit() after add()
• Expecting id to be set immediately after add()
• Confusing id with other attributes

5. You want to update a user's email in Flask ORM. Which approach best shows how ORM simplifies this compared to raw SQL?

user = User.query.filter_by(id=5).first()
user.email = '[e-mail]'
db.session.commit()

Why is this simpler than writing SQL?

hard

A. Because you must write raw SQL inside the Python code

B. Because you update the Python object directly without writing an UPDATE SQL statement

C. Because ORM automatically commits changes without calling commit()

D. Because you still need to write the full SQL UPDATE query manually

Solution

1. Step 1: Understand ORM object update

   You fetch the user as a Python object, change its attribute, and commit the session.

2. Step 2: Compare with raw SQL

   Raw SQL requires writing an UPDATE statement manually, but ORM lets you work with objects and attributes directly.

3. Final Answer:

   Because you update the Python object directly without writing an UPDATE SQL statement -> Option B

4. Quick Check:

   ORM updates objects, no manual SQL needed [OK]

Hint: ORM lets you change objects, not write SQL queries [OK]

Common Mistakes:

• Thinking ORM requires manual SQL for updates
• Assuming commit() is automatic
• Believing raw SQL is simpler than ORM