gitea-admin/gh-christianlouis-docuelevate
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge pull request #445 from christianlouis/copilot/enforce-database-upgrades-migration

Browse Source 
refactor(database): enforce Alembic-only schema migrations, deprecate manual migration code
This commit is contained in:
Christian Krakau-Louis
2026-03-01 18:22:48 +01:00
committed by GitHub
parent 08b24e3e66 8d81ed6c74
commit 8ac4179b8b
8 changed files with 655 additions and 114 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/DatabaseConfiguration.md
+9 -1
View File
@@ -163,7 +163,15 @@ DATABASE_URL=mysql+pymysql://user:password@host:3306/docuelevate?charset=utf8mb4
## Schema Migrations with Alembic
DocuElevate uses Alembic to manage all database schema changes.
DocuElevate uses Alembic **exclusively** to manage all database schema changes. On application startup, `init_db()` automatically applies any pending Alembic migrations, so the database schema is always kept in sync with the running code.
> **Note:** Prior to this change, a manual `_run_schema_migrations()` helper in `app/database.py` applied schema changes outside of Alembic. That function is now **deprecated** and will be removed in a future release. All schema changes are tracked as Alembic revisions in `migrations/versions/`.
### How It Works
1. **Fresh databases** — `Base.metadata.create_all()` creates all tables from the SQLAlchemy models, then Alembic stamps the version to `head` (no migrations need to run).
2. **Existing databases** — `alembic upgrade head` applies any pending migration scripts.
3. **CLI usage** — You can still run `alembic upgrade head` manually or in CI/CD before the application starts.
### Apply Migrations