By default DBLift is out of order meaning that any unapplied migration is eligible to be applied contrary to flyway which refuse to apply any migration with a lower version until you force it. You can still apply the original flyway model you can still opt-in with the —strict flag. https://docs.dblift.com/migrations-versioning
The main difference is the runtime, No JVM. If you already work in python DBLift integrates with your existing tooling: pip, sqlalchemy, Django, Flask…
Honest feedback welcome — especially if you're currently using Flyway on a Python project and it works fine, I'd like to understand what I'm missing. GitHub: https://github.com/dblift/dblift Docs: https://docs.dblift.com Move from Flyway: https://docs.dblift.com/move-from-flyway Supported databases: https://docs.dblift.com/supported-databases Ordering: https://docs.dblift.com/migrations-versioning

Discussion (2 Comments)Read Original on HackerNews