Is it possible to prevent column renames in migrations

When I delete a property and introduce another one with a similar name EF often creates a migrationBuilder.RenameColumn in the migration. But usually that’s not what I want and then I have to work around that by either splitting it up in two migrations or manually altering the created migration.

Is there a feature that I don’t know to tell maybe the Add-Migration command to not do column renames? Or do you have other best practices?

BR Matthias

EFCore 5.0.7, .Net 5.0, MSSQL

[ajcvickers]

Note from triage: this is not currently possible. Hopefully, #15178 will make this unnecessary. If not, we may consider this in a future release.

[icrocket]

Core makes a best effort to interpret changes and scaffold an appropriate starting point for the migration, but it should always be reviewed and edited when necessary for places where it doesn’t match the schema change desired.

Sure @ajcvickers, but we have a slightly different context: we create migrations starting from dynamic types compiled at runtime (Roslyn) and added to the DbContext models. In our case, the migrations are very simple (adding / removing fields) but we still encountered the “rename column” problem.

Therefore, in our single case, it would have been great to have a complete removal of that behavior as well.

As far as we are concerned, it will be enough for us to carry out atomic migrations (field by field). We will await your future feedback on improving the efcore migrations heuristics.

Thank you!