Dmitry, there is no way we can fix that in *-db-manage scripts. IMO, this is purely a deployment issue: from the code side we just can't guarantee you migration scripts will be applied correctly if you *are* changing the database during the process.
Dmitry, there is no way we can fix that in *-db-manage scripts. IMO, this is purely a deployment issue: from the code side we just can't guarantee you migration scripts will be applied correctly if you *are* changing the database during the process.