Does Alembic has the concept of versioned schemas/models? In Alembic, I need to re-define a model which matches the database table for the current migration. Becomes verbose after several migrations, redefining the same out-of-date model. So I created a "legacy_models" module where I define old models that don't match the current version. But I'm wondering if I'm reinventing the wheel?
I'm referring to the `table(...)` stuff mentioned here: https://www.georgevreilly.com/blog/2016/09/06/AlembicDataMigrations.html I have to repeat the "table" definition in every migration. But, for example, in Django a migration can refer to the version of the model at that point in time (when the migration was created) rather than the current version of a model which might have different columns. These model versions are automatically managed by Django. -- SQLAlchemy - The Python SQL Toolkit and Object Relational Mapper http://www.sqlalchemy.org/ To post example code, please provide an MCVE: Minimal, Complete, and Verifiable Example. See http://stackoverflow.com/help/mcve for a full description. --- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to sqlalchemy+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sqlalchemy/515d89c3-f48c-42ba-a2ba-e54753306276%40googlegroups.com.
