Consider adding simple database creation command to tooling

Open
#7,840 1 comment 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
csharp
Domain
databases, tooling

Research direction

Start by comparing the existing EnsureCreated() behavior with migration-based workflows and reviewing the current database tooling commands. The issue does not name files or tests; completion would require a settled command design, explicit limitations around migrations, and corresponding implementation and documentation.

Written by the indexing model from the issue text.

Description

area-tools blocked

(picking up an idea @rowanmiller mentioned today to make sure we have an opportunity to think it through)

Currently the minimal "getting started" workflows involve adding migrations and updating the database. This has the disadvantage that it goes high very quickly in terms of concept count. It seems to be desirable to have a simpler story.

One possible alternative would be to use the EnsureCreated() method, but it is not great to leave this in the code. In theory we could have a simple database create command that does the same as EnsureCreated(). This would be useful in all the same scenarios that EnsureCreated() is useful today, e.g. for rapid prototyping and testing but without the disadvantage of leaving that line of code in the code. Note that it would still have the disadvantage that there is no grow up story from EnsureCreated() into migrations, but that is something we could make explicit in the documentation, in the name of the command, and potentially in the output of the command.

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.