How to migrate after SQLalchemy schema changes?

When I set up my object mappings with SQLalchemy, everything works well enough. It even creates the tables for me if they don't exist.

However, if I decide to add/remove columns (aka fields) from an object, it starts erroring out with my old test data because it's got the old column set. Obviously I can drop my old test data and start over, but it's hard to generate new test data every time.

How can I make the old tables come back into sync again after changing SQLalchemy models? Or does SQLalchemy fundamentally require you to accept data loss in this situation?

is a duplicate

This question has been asked before and has already been answered. It should be marked as a duplicate.

Please enter the URL of the proposed duplicate in the details field below.

not constructive

This question cannot be answered in a way that is helpful to anyone. It's not possible to learn something from possible answers, except for the solution for the specific problem of the asker.

Communities

How to migrate after SQLalchemy schema changes?

2 comment threads

0 answers