Hi all, Is there anyway to tell alembic to store the history of all applied migrations and when they were applied instead of only saving the latest migration ?
Is there a reason only the latest migration is saved in the `alembic_version` table instead of saving the history of all applied migrations like django migrations or other tools from other languages like flyway or liquibase ? Regards, Samir -- You received this message because you are subscribed to the Google Groups "sqlalchemy-alembic" group. To unsubscribe from this group and stop receiving emails from it, send an email to sqlalchemy-alembic+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
