I’m using FM to deploy a database. As a part of that deploy, I’m rolling out a view. The changes go like this:
R1: create view
R2: no change to view
R3: add a column to the view
R4: no change
R5: remove the column from the view
The view is created by a script that is in source control. Let’s say that I deploy R3 and then decide that I should roll back to R2 (I’m thinking of a production site that I don’t want to leave in an odd state). So the view’s script (drop/create) is in a local file. I can’t use that script again because the local version is at R3 but I want it to go back to R1 (or R2).
How can I roll the view back to the previous version reliably using FluentMigrator? The only option I can think of is keeping the view create script in a string in my Migration class. But it seems like I’d need to have every version of it in a string in my class — very unwieldy and a hard sell to the team.
Every realistic solution to this that I can think of sort of goes against the idea of source control — having a single version of a thing locally and keeping track of its changes over time.
I added this feature into FluentMigrator — ability to execute a script straight from source. You can get it here:
https://github.com/jcollum/fluentmigrator
Currently only supports SVN. Hasn’t been integrated into the main branch yet.