💭 `ValueError: Constraint must have a name` in alembic 1.10.0 · ...
===================================================================

!https://github.com/sqlalchemy/alembic/issues/1195

Date: August 5, 2023

`ValueError: Constraint must have a name` in alembic 1.10.0 · Issue #1195 · sqlalchemy/alembic
 Describe the bug ValueError: Constraint must have a name in alembic 1.10.0. Expected behavior Migration succeeds. To Reproduce Please try to provide a Minimal, Complete, and Verifiable example, wit...
 GitHub · github.com [1]

After a nasty time with alembic upgrades, thoughts is about to get a new users table. This may have came from incorrectly setting up alembic for sqlite from the start, but I was able to fix the issue with this GitHub issue.

``` python
alembic sqlite ValueError: Constraint must have a name
```

The change I needed to make to get my migration to run.

``` diff - batch_op.create_foreign_key(None, 'user', ['author_id'], ['id'])

 + batch_op.create_foreign_key('fk_post_author_id_user', 'user', ['author_id'], ['id'])
```

!!! note

 This post is a thought [2]. It's a short note that I make
 about someone else's content online #thoughts [3]

References:
[1]: https://github.com/sqlalchemy/alembic/issues/1195
[2]: /thoughts/
[3]: /tags/thoughts/