4 ms·

Liquibase [0] is an alternative to FlywayDB. Unfortunately, FlywayDB changed their feature scope for the free version. [0] https://www.liquibase.org/ https://w

Liquibase [0] is an alternative to FlywayDB. Unfortunately, FlywayDB changed their feature scope for the free version. [0] https://www.liquibase.org/ https://www.liquibase.org/

smoyer 9y ago
I haven't run into a feature that I need from either of the paid plans. What features were removed that you find compelling? As an aside, Liquibase also effectively has a paid tier - it's just that it's marketed on a different web-site than the OSS version (http://www.datical.com/liquibase/ http://www.datical.com/liquibase/).
- einrealist 9y ago
  Dry-runs and rollbacks (Flyway's undos). Especially rollbacks are useful for development.
  - smoyer 9y ago
    I don't remember roll-backs ever being in the OSS project either. We always do potentially destructive operations in two different migrations since you'll never get data back once you delete it. We tend to favor soft-deletes anyway which makes life a lot easier but can bloat your DB.
  - oneweekwonder 9y ago
    > Especially rollbacks are useful for development I abuse Liquibase to generate sql for me by diffing a reference db to create the changeset. Will a rollback not be comparing your new schema against your old schema and then apply that changeset? Take into account this might/will drop data. But looking at flywaydb undo docs[0] I don't see it address anything more then the schema? [0]: https://flywaydb.org/documentation/command/undo https://flywaydb.org/documentation/command/undo edit: for those interested I recently moved my shell script solution to python[1]. [1]: https://github.com/Morabaraba/python-liquibase https://github.com/Morabaraba/python-liquibase
PaulKeeble 9y ago
Liquibase is missing some of the automated aspects that this blog post talks about but I know Nathan the developer is very amenable to people adding changes to the code base since I did that in the past with Sybase and SQL file support. I think more needs to be done to make always on migrations easier on the developers but it is doable.

Liquibase [0] is an alternative to FlywayDB. Unfortunately, FlywayDB changed their feature scope for the free version. [0] https://www.liquibase.org/ https://www.liquibase.org/

smoyer 9y ago

I haven't run into a feature that I need from either of the paid plans. What features were removed that you find compelling? As an aside, Liquibase also effectively has a paid tier - it's just that it's marketed on a different web-site than the OSS version (http://www.datical.com/liquibase/ http://www.datical.com/liquibase/).

einrealist 9y ago
Dry-runs and rollbacks (Flyway's undos). Especially rollbacks are useful for development.
- smoyer 9y ago
  I don't remember roll-backs ever being in the OSS project either. We always do potentially destructive operations in two different migrations since you'll never get data back once you delete it. We tend to favor soft-deletes anyway which makes life a lot easier but can bloat your DB.
- oneweekwonder 9y ago
  > Especially rollbacks are useful for development I abuse Liquibase to generate sql for me by diffing a reference db to create the changeset. Will a rollback not be comparing your new schema against your old schema and then apply that changeset? Take into account this might/will drop data. But looking at flywaydb undo docs[0] I don't see it address anything more then the schema? [0]: https://flywaydb.org/documentation/command/undo https://flywaydb.org/documentation/command/undo edit: for those interested I recently moved my shell script solution to python[1]. [1]: https://github.com/Morabaraba/python-liquibase https://github.com/Morabaraba/python-liquibase

PaulKeeble 9y ago

Liquibase is missing some of the automated aspects that this blog post talks about but I know Nathan the developer is very amenable to people adding changes to the code base since I did that in the past with Sybase and SQL file support. I think more needs to be done to make always on migrations easier on the developers but it is doable.