Roll back ideas

[csd...@gmail.com]

I'm curious how others have handled roll back when it is legitimate, for instance if you switch from working on a feature to an emergency production fix. In this scenario your feature work may have applied one or more transitions that modified your local database in a way that's fundamentally incompatible with the current production schema. If you switch branches from a feature to a hotfix then those feature transition scripts will not be present and yet you'll be left in a state where you need to get your database looking like production. What is the appropriate thing to do in this case? Manually undo the feature changes? Backup and restore from production database? Etc.

[Casper Schmidt Wandahl-Liper]

Where I currently work we have a script to create a copy of the "master"-database (database for latest release). This new copy is for developing the new feature. This would require some manual change to the configuration to switch from feature-db til master-db or having multiple local copies.

Venlig hilsen/Kind regards
Casper S. Wandahl-Liper

--
You received this message because you are subscribed to the Google Groups "DbUp Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dbup-discuss...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.