Warn when migration script has changed

[jpoehls]

A big pothole with migrations is when someone changes a migration script after it has already been run. Can we find someway to warn/break when this happens? RoundhouseE DB has some logic to check for this. (http://www.google.com/url?sa=D&q=http%3A%2F%2Fferventcoder.com%2Farchive%2F2009%2F11%2F13%2Froundhouse-db-migration-action-shots.aspx)

[kieranbenton]

We are using DotNetMigrations in anger now and we don't really have a satisfactory answer to this yet - if you have any experience to offer I'd love to discuss it.

[jpoehls]

Currently the only advice I can offer here is discipline. If you have checked-in a migration script, don't change it. Ever. If you follow that rule then all should be well.