{"id":49447202,"title":"Show HN: DBLift – database migration management for Python teams","points":5,"user":"cmodiano","time":1787744129,"time_ago":"17 hours ago","type":"link","content":"

I’ve been working for a while on DBLift, an open-source database migration toolkit for Python teams.\nDBLift follows the same model flyway does with the same main commands and the same history table structure making it easy to switch from one to the other with the import_flyway command.

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.\nGitHub: 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","url":"https://dblift.com/","domain":"dblift.com","comments":[{"id":49448553,"level":0,"user":"tianzhou","time":1787750012,"time_ago":"15 hours ago","content":"

Congrats on the launch, good project name and glad to see new project trying to address the classic schema migration problem.","comments":[{"id":49451520,"level":1,"user":"cmodiano","time":1787760493,"time_ago":"12 hours ago","content":"

Thank you very much, there are a lot of them already, tried to address the Python ecosystem integration to the maximum.","comments":[]}]}],"comments_count":2}