Improve experience deploying databases created by Migrations
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
Research direction
This is an umbrella issue rather than a self-contained task, with completed and backlog work tracked through the referenced issue numbers. Start by reviewing the backlog items and their individual scopes; no file, test, entry point, or single definition of done is provided here, so a contributor should select a concrete child issue before beginning.
Written by the indexing model from the issue text.
Description
This is a grouping of related issues. Feel free to vote (👍) for this issue to indicate that this is an area that you think we should spend time on, but consider also voting for individual issues for things you consider especially important.
Currently, many developers migrate their databases at application startup time. This is easy but is not recommended because:
- Multiple threads/processes/servers may attempt to migrate the database concurrently
- Applications may try to access inconsistent state while this is happening
- Usually the database permissions to modify the schema should not be granted for application execution
- Its hard to revert back to a clean state if something goes wrong
We want to deliver a better experience here that allows an easy way to migrate the database at deployment time. This should:
- Work on Linux, Mac, and Windows
- Be a good experience on the command line
- Support scenarios with containers
- Work with commonly used real-world deployment tools/flows
- Integrate into at least Visual Studio
The result is likely to be many small improvements in EF Core (for example, better Migrations on SQLite), together with guidance and longer-term collaborations with other teams to improve end-to-end experiences that go beyond just EF.
Done in 6.0
- #19693
Done in 9.0
- #22616
- #17578
- #33731
- #33732
Backlog
- #17568
- #2167
- #3053
- #8695
- #15174
- #29343
- #15762
- #16406
- #18624
- #18840
- #20402
- #22613
- #24866
- #25872
- #31999
- #26155
- #19694
- #24710
- #34991
- Dominant language
- C#
- Stars
- 14.8k
- Forks
- 3.4k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 134
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from dotnet/efcore
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
-
customer-reported
Difficulty 5/5 Over a week Newbie friendliness 38/100
-
area-cosmos area-vector-search
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
area-cosmos
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
area-tools needs-design
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
:watch: Not Triaged 11.0 fundamentals/subsvc
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
dotnet/AspNetCore.Docs#37699 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
SubtitleEdit/subtitleedit#15108 · 1 comment ·
-
area/docs-content Bug pulumi/docs
Difficulty 1/5 1-3 hours Newbie friendliness 94/100
-
agentic-workflows untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 76/100