We ran into a fairly esoteric bug when trying to roll back some migrations
(in dev, thankfully!). The effect is an infinite loop in
Migrator.MigrateTo(long), I think it may be caused by the fact that we have
version numbers in the database that don't match up to a migration in the
assembly (they're split across multiple assemblies, is that a bad idea?).
I've attached a patch with a test that replicates the issue. We've also got
a fix, but it's not pretty (a "stop" flag in BaseMigrate.NextMigration()).
Original issue reported on code.google.com by grahamr...@gmail.com on 30 Dec 2009 at 10:16
Original issue reported on code.google.com by
grahamr...@gmail.comon 30 Dec 2009 at 10:16Attachments: