fastapi-postgres-repository

Bulk upsert in a FastAPI PostgreSQL repository uses the ON CONFLICT SQL clause to insert or update multiple records in a single database round trip. This approach leverages SQLAlchemy AsyncSession to efficiently handle batch data synchronization.

Soft delete filtering for SQLAlchemy async models is handled automatically via a SoftDeleteMixin. This mixin intercepts queries to exclude deleted records natively, while also providing optional restoration support to recover soft-deleted entries when needed.

Paginated and filtered CRUD endpoints in FastAPI are set up by integrating fastapi-pagination and fastapi-filter with your SQLAlchemy AsyncSession. The repository layer connects these libraries to provide seamless, queryable data access without duplicating code.

Yes, fastapi-pagination integrates seamlessly with a custom PostgreSQL repository pattern built on SQLAlchemy AsyncSession. The repository handles the data access logic, while fastapi-pagination manages the pagination constraints and response formatting.

You create an entity-specific repository by inheriting from the flexible PostgresRepository base class and supplying your specific SQLAlchemy model and Pydantic schemas. This allows easy extension for custom data access while reusing bulk upsert and soft delete features.

Yes, soft delete in this repository pattern supports optional restoration of deleted records. The SoftDeleteMixin automatically filters deleted entries from standard queries while retaining the ability to recover them when business logic requires it.