I developed some wrappers for SQLAlchemy session for using in repositories in FastAPI application to ensure that there is only one single session per request. The final goal for this is to incapsulate working with session in autocommit mode (like for example in Django). The whole code is in my GitHub repository.

I developed some wrappers for SQLAlchemy session for using in repositories in FastAPI application to ensure that there is only one single session per request. The final goal for this is to incapsulate working with session in autocommit mode (like for example in Django). The whole code is in my GitHub repository.

I developed some wrappers for SQLAlchemy session for using in repositories in FastAPI application to ensure that there is only one single session per request. The final goal for this is to incapsulate working with session in autocommit mode (like for example in Django). The whole code is in my GitHub repository.

I developed some wrappers for SQLAlchemy session for using in repositories in FastAPI application to ensure that there is only one single session per request. The final goal for this is to incapsulate working with session in autocommit mode (like for example in Django). The whole code is in my GitHub repository.

I have written this endpoint in fastapi and sqlalchemy

I created a function that checks the data from environment variables about the first owner and creates it if it doesn’t exist. If I use this function in a route, it works correctly, but if I add it to the lifespan function, I get an error.

I have a table for users, series, and movies, and I need to create a ‘Watchlist’ table that includes the movies and series a user plans to watch in the future. How is this best implemented? I understand how to link just two tables, but I struggle when it comes to three.

I am using fastapi for the first time, and I divided my project into two parts which are admin (used django) and api (fastapi). First I defined my models in django and migrated, and connect fastapi to the existing db.
models.py

This is driving me crazy. As an example, I have a many-to-many relationship between tables called labels and tasks. Take this code excerpt for a filtered record:

I have some list of unique user_ids which located in several different tables and I want to pull the user out with only one SELECT statement (at least in code).
I have these ORM models in my models.py: