Alembic
A database migration tool built on SQLAlchemy, used to manage the versioned evolution of database schemas.
Core Facts
Timeline (last 90 days)
SurplusLink AI uses PostgreSQL to manage relational data, with SQLAlchemy and Alembic handling model definitions and versioned migrations.
HireLens AI's frontend stack is Next.js 14, React and Tailwind CSS; the backend is Python, FastAPI and Pydantic; the database is PostgreSQL with SQLAlchemy and Alembic; background tasks use Celery and Redis; and the AI part integrates open-weight models via Ollama.
StockSense's tech stack is: frontend Next.js 16, React 19, TypeScript, Tailwind CSS, Recharts; API is Python, FastAPI, SQLAlchemy, Pydantic; SQLite for local development, PostgreSQL for the Docker Compose path; uses Alembic migrations.
The fix for #573 is to verify during restore whether the actual schema head matches the manifest, and refuse to execute if they do not match.
In defect #573, the backup manifest pinned alembic_head to 0034, while the live schema head was already 0035; the restore operation would succeed but restore to the wrong version.
Alembic is a database migration tool in the SQLAlchemy ecosystem; each migration script has an independent version identifier forming a migration chain, the end of the chain is called the head, and alembic_head records the last migration that the current database has applied.
LectuLibre's tech stack is Python/FastAPI + PostgreSQL, with SQLAlchemy 2.0 async mode plus the asyncpg driver for the ORM, and migrations managed by Alembic.
AI Python Mentor's back-end tech stack uses Python 3.12, FastAPI, and PostgreSQL, together with SQLAlchemy, Alembic, and Pydantic, and is based on the AsyncIO asynchronous model.
Common database migration tools include Flyway, Liquibase, and Rails Active Record Migrations.
All Facts (10)
Alembic is a database migration tool in the SQLAlchemy ecosystem, developed by SQLAlchemy's author Mike Bayer.
65%UnverifiedSurplusLink AI uses PostgreSQL to manage relational data, with SQLAlchemy and Alembic handling model definitions and versioned migrations.
50%UnverifiedHireLens AI's frontend stack is Next.js 14, React and Tailwind CSS; the backend is Python, FastAPI and Pydantic; the database is PostgreSQL with SQLAlchemy and Alembic; background tasks use Celery and Redis; and the AI part integrates open-weight models via Ollama.
50%UnverifiedStockSense's tech stack is: frontend Next.js 16, React 19, TypeScript, Tailwind CSS, Recharts; API is Python, FastAPI, SQLAlchemy, Pydantic; SQLite for local development, PostgreSQL for the Docker Compose path; uses Alembic migrations.
50%UnverifiedThe fix for #573 is to verify during restore whether the actual schema head matches the manifest, and refuse to execute if they do not match.
50%UnverifiedAlembic is a database migration tool in the SQLAlchemy ecosystem; each migration script has an independent version identifier forming a migration chain, the end of the chain is called the head, and alembic_head records the last migration that the current database has applied.
50%UnverifiedLectuLibre's tech stack is Python/FastAPI + PostgreSQL, with SQLAlchemy 2.0 async mode plus the asyncpg driver for the ORM, and migrations managed by Alembic.
50%UnverifiedAI Python Mentor's back-end tech stack uses Python 3.12, FastAPI, and PostgreSQL, together with SQLAlchemy, Alembic, and Pydantic, and is based on the AsyncIO asynchronous model.
50%UnverifiedCommon database migration tools include Flyway, Liquibase, and Rails Active Record Migrations.
50%UnverifiedIn defect #573, the backup manifest pinned alembic_head to 0034, while the live schema head was already 0035; the restore operation would succeed but restore to the wrong version.
50%