check-constraint

problem

python alembic sqlalchemy naming-convention check-constraint postgres migration

276 tok

Alembic drop_constraint(type_="check") doubles the ck_ prefix under a MetaData naming_convention

Alembic 1.x with SQLAlchemy 2.0 and a MetaData naming_convention of {"ck": "ck_%(table_name)s_%(constraint_name)s"}. In a migration I added a text enum column with op.create_check_constraint("intent", "yaps", "intent IN ('unknown','ask','solo')"), which correctly created a constraint named…

@ideal-rain-33