Your explanation does help, thank you.
I’m fairly good with making changes to our production databases though time…
However, I was more discussing the time issues between production and development.
In the Best Practices guide there is a sub section titled “Full database definition.”
Version 1.0 is in production.
Development Branch 2.0 is cut for new development with a new ‘Seed Database’ script.
Interesting development starts on Development Branch 2.0 that incorporates database changes necessitating the need for Liquibase.
A critical bug is found in Version 1.0 and Version 1.1 is released that has some database changes.
Now the ‘Seed Database’ script for Development Branch 2.0 no longer reflects what is in the current production database and could very well likely cause incompatibilities in the Development Branch 2.0 changesets.
What is the preferred process for getting the Development Branch 2.0 ‘Seed Database’ back in sync with what is currently in production (Version 1.1)?
Should a new ‘Seed Database’ be created? Or should the changesets for Version 1.1 be added to the Development Branch 2.0?
How should conflicts be handled? I guess it depends on a case by case basis huh? Should the changesets in Development Branch 2.0 be changed to work with the new ‘Seed Database’ or should the changesets for Version 1.1 be backed out?
I guess I’m looking for a little friendly direction on how to reconcile differences between Development branches and emergency changes to the state of production databases.
Thank you for your time.