context-async-sqlalchemy 2.1.7

A convenient way to configure and work with an async SQLAlchemy session through context in asynchronous applications

context-async-sqlalchemy

(coverage > 90%)

DOCUMENTATION

Provides a super convenient way to work with SQLAlchemy in asynchronous applications. It handles the lifecycle management of the engine, sessions, and transactions.

The main goal is to provide quick and easy access to a session, without worrying about opening or closing it when it’s not necessary.

Key features:

• Automatically manages the lifecycle of the engine, sessions, and transactions
• Allows for user autonomy when manually opening or closing sessions and transactions
• Framework-agnostic
• Not a wrapper around SQLAlchemy
• Convenient for testing
• Runtime host switching
• Supports multiple databases and sessions per database
• Provides tools for running concurrent SQL queries
• Fully lazy initialization

Example of a typical session

from context_async_sqlalchemy import db_session
from sqlalchemy import insert

from database import connection  # your configured connection to the database
from models import ExampleTable  # a model for example

async def some_func() -> None:
    # Creates a session with no connection to the database yet
    session = await db_session(connection)
    
    stmt = insert(ExampleTable).values(text="example_with_db_session")

    # A connection and transaction open in the first request.
    await session.execute(stmt)
    
    # If you call db_session again, it returns the same session
    # even in child coroutines.
    session = await db_session(connection)
    
    # The second request uses the same connection and the same transaction
    await session.execute(stmt)

    # The commit and closing of the session occurs automatically

How it works

1. Before executing your code, the middleware prepares a container in which the sessions required by your code are stored. The container is saved in contextvars.
2. Your code accesses the library to create new sessions and retrieve existing ones.
3. The middleware automatically commits or rolls back open transactions. It also closes open sessions and clears the context.

The library provides the ability to commit, roll back, and close at any