`Valueerror: Constraint Must Have A Name` In Alembic 1.10.0 · Issue #1195 · Sqlalchemy/Alembic


Here's my thought on ValueError: Constraint must have a name in alembic 1.10.0 · Issue #1195 · sqlalchemy/alembic

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.

alembic sqlite ValueError: Constraint must have a name

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

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

This post was a thought by Waylon Walker see all my thoughts at https://waylonwalker.com/thoughts