docs: add Alembic sequential migration numbering rule to CLAUDE.md (#38)
Migrations must use sequential numbered prefixes (e.g., 040_desc.py) with --rev-id flag. Never use auto-generated revision IDs. Updated both the lessons learned section and the development commands. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
@@ -166,7 +166,7 @@ cd frontend && npm run build
|
|||||||
|
|
||||||
# Database migrations
|
# Database migrations
|
||||||
cd backend && alembic upgrade head
|
cd backend && alembic upgrade head
|
||||||
alembic revision --autogenerate -m "Description"
|
alembic revision --autogenerate -m "Description" --rev-id=NNN # NNN = next sequential number
|
||||||
|
|
||||||
# Access PostgreSQL
|
# Access PostgreSQL
|
||||||
docker exec -it patherly_postgres psql -U postgres -d patherly
|
docker exec -it patherly_postgres psql -U postgres -d patherly
|
||||||
@@ -304,6 +304,8 @@ navigate(`/trees/${newTree.id}/edit`)
|
|||||||
|
|
||||||
**37. First deployed user needs manual admin promotion:** New users default to `engineer` role. Promote via SQL: `UPDATE users SET role = 'admin' WHERE email = '...';` then re-login for new JWT.
|
**37. First deployed user needs manual admin promotion:** New users default to `engineer` role. Promote via SQL: `UPDATE users SET role = 'admin' WHERE email = '...';` then re-login for new JWT.
|
||||||
|
|
||||||
|
**38. Alembic migrations MUST use sequential numbered prefixes:** Check `backend/alembic/versions/` for the highest numbered migration and use the next number. Format: `XXX_descriptive_name.py` (e.g., `040_add_whatever.py`). NEVER use auto-generated revision IDs like `0f1ca2af3647`. Always pass `--rev-id` flag: `alembic revision --autogenerate -m "desc" --rev-id=040`.
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
## RBAC & Permissions
|
## RBAC & Permissions
|
||||||
|
|||||||
Reference in New Issue
Block a user