Let's suppose we have the following scenario:
1 prod database, and one dev database
Each of these dev databases cannot be dropped/scaffolded, and they'll always live on as they are.
Along with that, there are multiple hosted instances of a web application, on different domains.
As an example, let's say we have 4 domains, 1 for production, and 3 for development.
All the 3 dev domains use the same dev database.
If we have 3 teams, and each takes one dev environment, how would we deal with migrations during the development phases?
What if we want to experiment with things on these databases, and we don't want them to count as migrations?
The thing I'm struggling with is how can team X make changes to a DB, but doesn't want to make a migration out of it, and in parallel, team Y makes other changes as well that might meddle with the ones that team 1 (and maybe even team Z) is working on?
The problem is that we can't have local databases (for reasons that we won't be discussing here)
How can we deal with this using flyway? I don't think making migrations and then "undoing" them is an option here, is it ?
Thanks a lot in advance for the help, and I can clarify this further if needed.
