❔ EF Core migrations

Is it normal that when I do

ef database update

ef database update

with an unapplied migration, it tries applying all migrations from the start, even though the database already has all of the migrations but the last one? Like it even has a table with migration history so it should automatically detect which migrations haven't been applied yet. Or am I wrong?

Communities Docs About Terms Privacy

❔ EF Core migrations

Similar Threads

❔ EF Core migrations

Similar Threads

Similar Threads

Similar Threads