Skip to content
Discussion options

You must be logged in to vote

PK changes are not part of autogenerate right now. There's a layer of impracticality to PK changes which is that the correct migrations to modify the PK of a table can be very complicated as the PK constraint can typically only be dropped and recreated, which is often infeasible as it's the target of foreign key constraints from elsewhere.

see also https://alembic.sqlalchemy.org/en/latest/autogenerate.html#what-does-autogenerate-detect-and-what-does-it-not-detect

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by david-fed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants