Database query optimization in Flask - Step-by-Step Execution

Concept Flow - Database query optimization

Write Query in Flask

↓

Send Query to DB

↓

DB Executes Query

↓

Check Query Performance

↓

Optimize Query

↓

Repeat Until Fast Enough

↓

Return Results to Flask

This flow shows how a Flask app sends a database query, checks its speed, and improves it step-by-step.

Execution Sample

Flask

from flask_sqlalchemy import SQLAlchemy

# Slow query example
users = User.query.filter(User.age > 20).all()

This code fetches all users older than 20 from the database using Flask-SQLAlchemy.

Execution Table

Step	Action	Query Sent	Execution Time	Optimization Applied	Result
1	Initial query sent	SELECT * FROM users WHERE age > 20;	500ms	None	All users > 20 fetched
2	Add index on age column	Same query	50ms	Index on age	Faster fetch of users > 20
3	Select only needed columns	SELECT id, name FROM users WHERE age > 20;	30ms	Column selection	Less data fetched
4	Limit results for pagination	SELECT id, name FROM users WHERE age > 20 LIMIT 10;	10ms	Limit results	Only 10 users fetched
5	Query optimized enough	N/A	N/A	Stop optimization	Return results to Flask

💡 Optimization stops when query runs fast enough for app needs.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	Final
Execution Time	N/A	500ms	50ms	30ms	10ms	10ms
Query	N/A	SELECT * FROM users WHERE age > 20;	Same query	SELECT id, name FROM users WHERE age > 20;	SELECT id, name FROM users WHERE age > 20 LIMIT 10;	Final optimized query
Result Size	N/A	Large	Large	Smaller	Small	Small

Key Moments - 3 Insights

Why does adding an index speed up the query so much?

Adding an index lets the database find rows faster without scanning the whole table, as shown by the drop from 500ms to 50ms in execution time in the execution_table.

Why select only needed columns instead of *?

Selecting only needed columns reduces data sent over the network and memory used, making the query faster, as seen in step 3 where execution time drops from 50ms to 30ms.

What does limiting results do for performance?

Limiting results reduces the number of rows fetched, which speeds up response time and reduces load, shown in step 4 where time drops to 10ms.

Visual Quiz - 3 Questions

Look at the execution_table, what is the execution time after adding an index on the age column?

A 500ms

B 50ms

C 30ms

D 10ms

💡 Hint

Check the 'Execution Time' column at step 2 in the execution_table.

At which step does the query start selecting only specific columns instead of all columns?

A Step 1

B Step 2

C Step 3

D Step 4

💡 Hint

Look at the 'Query Sent' column in the execution_table to see when SELECT changes.

If we remove the LIMIT clause in step 4, what would likely happen to execution time?

A It would increase

B It would decrease

C It would stay the same

D It would become zero

💡 Hint

Refer to the execution_table row for step 4 and think about how LIMIT affects result size.

Concept Snapshot

Database query optimization in Flask:
- Write query with SQLAlchemy
- Add indexes to speed up searches
- Select only needed columns
- Use LIMIT for pagination
- Repeat optimization until query is fast
- Return results to Flask app

Full Transcript

This visual trace shows how a Flask app sends a database query and improves it step-by-step. Initially, the query selects all users older than 20, taking 500ms. Adding an index on the age column reduces time to 50ms by helping the database find rows faster. Selecting only needed columns reduces data size and time to 30ms. Adding a LIMIT clause fetches fewer rows, speeding up to 10ms. Optimization stops when the query runs fast enough. Variables like execution time and query text change at each step. Key moments explain why indexes, column selection, and limits improve speed. Quiz questions check understanding of these steps.