Migrations: Full table drop/create scaffolded when CLR type renamed or base type introduced

Open
#5,826 2 comments 8 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
csharp
Domain
databases

Research direction

Review EF6's table-rename detection and EF Core's migration scaffolding for CLR type renames or introduced base types. Reproduce the case with a data-bearing target table and inspect the generated migration; done means the scaffold preserves data via a rename rather than requiring a hand-written migration.

Written by the indexing model from the issue text.

Description

area-migrations

In EF6 we would very often detect this case directly and do a table rename. In Core, if the target table has data, it looks like the user basically has to scrape the generated migration and write if from scratch.

Dominant language
C#
Stars
14.8k
Forks
3.4k
Avg merge
2d 5h
Merged PRs (30d)
134

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dotnet/efcore

All issues in dotnet/efcore

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.