In the middle of a migration, it's better to use Sql()
method to update database data.
Sql("UPDATE dbo.RequestValidationErrors SET IsBreaking = 0 WHERE WordCode = 'RequestValidationError.MoreThanOneItemFound'");
Also you should define the default value for the new column. So the solution should be something like this:
public override void Up()
{
AddColumn("dbo.RequestValidationErrors", "IsBreaking", c => c.Boolean(nullable: false, default: true));
Sql("UPDATE dbo.RequestValidationErrors SET IsBreaking = 0 WHERE WordCode = "RequestValidationError.MoreThanOneItemFound"");
}
Using a DbContext
in the middle of its migration is very ambiguous. What do you expect from the context? It has the after migration state in its models, but the database has the before migration state in the tables. So the model and database do not match. If you still insist on using DbContext
in your code, disabling the model checking might be the solution. You can disable model checking using:
Database.SetInitializer<Log4ProContext>(null);
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…