Consider Migrations behavior when store-generated GUID doesn't have DefaultValueSql set
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Start by reading issue #14518 and tracing how generated values without a value generator are handled by the update pipeline and Migrations. Compare the proposed warning, model-validation warning, and convention-based default approaches, including SQL Server's newsequentialid(). Done requires a decided behavior for existing databases and migration-created databases.
Written by the indexing model from the issue text.
Description
See issue #14518. In this case, the property should be treated as store-generated by the update pipeline because:
- It is configured to have a generated value
- It has no associated value generator
This makes sense when the database already exists, but if the database is being created by migrations then we don't know what default constraint makes sense. Options discussed were:
- Warn in Migrations (may need us to build a mechanism to do so)
- Warn in model validation (warning will be shown even when database exists and is fine)
- Set a sensible default constraint by convention (for example,
newsequentialid()for GUIDs on SQL Server; less clear what makes sense for other types and other providers.)
- 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