Async database queries in FastAPI - Step-by-Step Execution

Concept Flow - Async database queries

Start API request

↓

Call async DB query function

↓

Await DB response

↓

DB processes query asynchronously

↓

Return data to API

↓

Send response to client

↓

End request

This flow shows how an async database query is called and awaited in FastAPI, allowing the server to handle other tasks while waiting for the database.

Execution Sample

FastAPI

from fastapi import FastAPI
from databases import Database

app = FastAPI()
db = Database('sqlite:///test.db')

@app.on_event("startup")
async def startup():
    await db.connect()

@app.on_event("shutdown")
async def shutdown():
    await db.disconnect()

@app.get('/items/{id}')
async def read_item(id: int):
    query = 'SELECT * FROM items WHERE id = :id'
    return await db.fetch_one(query=query, values={'id': id})

This code defines an async FastAPI endpoint that queries a database asynchronously for an item by id.

Execution Table

Step	Action	Awaited?	DB Query Sent	DB Response Received	API Response Sent
1	API receives GET /items/5	No	No	No	No
2	Call read_item(5)	Yes	No	No	No
3	Await db.fetch_one(query, values)	Yes	Yes	No	No
4	DB processes query asynchronously	Yes	Yes	Yes	No
5	Await completes with data	No	Yes	Yes	No
6	Return data from read_item	No	Yes	Yes	Yes
7	API sends response to client	No	Yes	Yes	Yes
8	Request handling complete	No	Yes	Yes	Yes

💡 Request ends after sending API response with data from async DB query.

Variable Tracker

Variable	Start	After Step 3	After Step 5	Final
id	undefined	5	5	5
query	undefined	SELECT * FROM items WHERE id = :id	SELECT * FROM items WHERE id = :id	SELECT * FROM items WHERE id = :id
db_response	undefined	awaiting	{'id': 5, 'name': 'Item 5'}	{'id': 5, 'name': 'Item 5'}
api_response	undefined	undefined	undefined	{'id': 5, 'name': 'Item 5'}

Key Moments - 3 Insights

Why do we use 'await' before the database query?

Because the database query is asynchronous, 'await' pauses the function until the data is ready, as shown in execution_table step 3 and 5.

What happens if we don't use 'await' on the async DB call?

The function would return a coroutine object instead of actual data, so the API response would be incorrect. See step 5 where awaiting completes with data.

Does the server block other requests while waiting for the DB?

No, because the async call allows the server to handle other tasks during the wait, as the DB processes query asynchronously in step 4.

Visual Quiz - 3 Questions

Look at the execution table, at which step is the database query actually sent?

A Step 3

B Step 2

C Step 5

D Step 1

💡 Hint

Check the 'DB Query Sent' column in the execution_table.

According to variable_tracker, what is the value of 'db_response' after step 5?

A 'awaiting'

B {'id': 5, 'name': 'Item 5'}

C undefined

D 5

💡 Hint

Look at the 'db_response' row and 'After Step 5' column in variable_tracker.

If we remove 'await' before db.fetch_one, what will happen to the API response?

A It will cause a syntax error

B It will return the actual data immediately

C It will return a coroutine object, not the data

D It will block the server until data arrives

💡 Hint

Refer to key_moments about the importance of 'await' and execution_table step 5.

Concept Snapshot

Async database queries in FastAPI:
- Use async def for endpoint functions
- Use 'await' to pause until DB query completes
- DB queries run without blocking server
- Return awaited data as API response
- Enables handling many requests efficiently

Full Transcript

This visual execution trace shows how FastAPI handles async database queries. When the API receives a request, it calls an async function that sends a query to the database using 'await'. The server does not block but waits asynchronously for the database to respond. Once the data arrives, the function returns it, and the API sends the response to the client. Variables like 'db_response' change from 'awaiting' to actual data after the await completes. Key points include the necessity of 'await' to get real data and how async queries improve server responsiveness.

Practice

1. What is the main benefit of using async database queries in FastAPI?

easy

A. It removes the need for database connections.

B. It makes the database run faster internally.

C. The app can handle other tasks while waiting for the database response.

D. It automatically caches all database results.

Solution

1. Step 1: Understand async behavior in FastAPI

   Async lets the app continue running other code instead of waiting for slow operations like database queries.

2. Step 2: Identify the benefit of async database queries

   This means the app stays responsive and can handle more requests while waiting for the database.

3. Final Answer:

   The app can handle other tasks while waiting for the database response. -> Option C

4. Quick Check:

   Async = non-blocking tasks [OK]

Hint: Async means do other work while waiting [OK]

Common Mistakes:

• Thinking async speeds up the database itself
• Believing async caches results automatically
• Assuming async removes database connections

2. Which of the following is the correct way to define an async function for a database query in FastAPI?

easy

A. async def get_data(): return await session.execute(query)

B. async def get_data(): return session.execute(query)

C. def get_data(): return await session.execute(query)

D. def get_data(): return session.execute(query)

Solution

1. Step 1: Recognize async function syntax

   Async functions must be declared with async def to use await inside.

2. Step 2: Match correct usage of await

   To wait for the database query, await must be used with the async session call.

3. Final Answer:

   async def get_data(): return await session.execute(query) -> Option A

4. Quick Check:

   Async function + await = correct syntax [OK]

Hint: Use async def with await inside async functions [OK]

Common Mistakes:

• Missing async keyword but using await
• Using await without async function
• Calling async functions without await

3. Given this async function in FastAPI using SQLAlchemy async session:

async def fetch_users(session):
    result = await session.execute("SELECT name FROM users")
    users = result.scalars().all()
    return users

What will fetch_users return?

medium

A. A coroutine object that needs awaiting

B. A list of user names from the database

C. A SQLAlchemy Result object

D. An error because scalars() is not async

Solution

1. Step 1: Understand await on session.execute

   The await waits for the query to finish and returns a Result object.

2. Step 2: Use scalars().all() on Result

   Calling scalars().all() extracts all values from the first column as a list.

3. Final Answer:

   A list of user names from the database -> Option B

4. Quick Check:

   await + scalars().all() = list output [OK]

Hint: await session.execute returns Result; scalars().all() gives list [OK]

Common Mistakes:

• Thinking fetch_users returns a coroutine, not awaited
• Expecting a Result object instead of list
• Assuming scalars() is async and causes error

4. Identify the error in this FastAPI async database query code:

async def get_items(session):
    result = session.execute("SELECT * FROM items")
    return await result.fetchall()

medium

A. Function should not be async

B. Cannot await fetchall() method

C. session.execute should not be async

D. Missing await before session.execute call

Solution

1. Step 1: Check usage of async session.execute

   session.execute is an async method and must be awaited to get the Result.

2. Step 2: Understand fetchall() usage

   fetchall() is called on the awaited Result; awaiting fetchall() is incorrect because it returns a list synchronously.

3. Final Answer:

   Missing await before session.execute call -> Option D

4. Quick Check:

   await session.execute needed before fetchall() [OK]

Hint: Always await async session.execute calls first [OK]

Common Mistakes:

• Not awaiting session.execute causing coroutine error
• Awaiting fetchall() which is not async
• Confusing async with sync methods

5. You want to fetch all active users asynchronously and return their emails in FastAPI. Which code snippet correctly uses async database queries and filters results?

hard

A. async def get_active_emails(session):
result = await session.execute("SELECT email FROM users WHERE active=1")
return result.scalars().all()

B. def get_active_emails(session):
result = session.execute("SELECT email FROM users WHERE active=1")
return result.scalars().all()

C. async def get_active_emails(session):
result = session.execute("SELECT email FROM users WHERE active=1")
return await result.scalars().all()

D. async def get_active_emails(session):
result = await session.execute("SELECT email FROM users")
return [email for email in result.scalars().all() if email.active == 1]

Solution

1. Step 1: Use async def and await session.execute

   The function must be async and await the async session.execute call with the correct SQL filter.

2. Step 2: Extract emails with scalars().all()

   Calling scalars().all() on the awaited result returns a list of emails matching the filter.

3. Final Answer:

   async def get_active_emails(session): result = await session.execute("SELECT email FROM users WHERE active=1") return result.scalars().all() -> Option A

4. Quick Check:

   Async + await + filtered query = correct [OK]

Hint: Await session.execute with filter, then scalars().all() [OK]

Common Mistakes:

• Using sync def with async calls
• Not awaiting session.execute
• Filtering results in Python instead of SQL