Flyway is just SQL commands. It's really simple to read in code reviews and if there's a conflict it's a pain but it can all be fixed.
As you said, Liquibase conflicts are really hard to read and follow. Then redoing the process is painful.
I agree that we should segment DB features better. Unfortunately that wasn't my call on the team. The features are sometimes concurrent and backported so you end up with different schemas all over the place and people going back/forth between schemas.
All the teams are vertical/feature oriented so everyone touches the database all the time.
I can't say we love Flyway. It just fails in a way that's easier to understand.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Flyway is just SQL commands. It's really simple to read in code reviews and if there's a conflict it's a pain but it can all be fixed.
As you said, Liquibase conflicts are really hard to read and follow. Then redoing the process is painful.
I agree that we should segment DB features better. Unfortunately that wasn't my call on the team. The features are sometimes concurrent and backported so you end up with different schemas all over the place and people going back/forth between schemas.
All the teams are vertical/feature oriented so everyone touches the database all the time.
I can't say we love Flyway. It just fails in a way that's easier to understand.