Mapping attribute to create alternate keys

Open
#23,153 4 comments 0 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
database

Research direction

Start by reviewing the relationship between this proposal and issue #4073, which the description identifies as a prerequisite. Then determine the intended attribute and mapping behavior for alternate keys, including unique columns or column groups and their possible use as relationship principals. Done means the design and implementation support that behavior without the stated #4073 limitation.

Written by the indexing model from the issue text.

Description

area-model-building

Ultimately this will create a unique column (or group of columns) in the database which may or may not be used as the principal end of a relationship. In other words, it's a way to make a non-primary key column have a unique constraint without explicitly specifying a unique index.

This is not technically blocked on #4073, but should probably not be implemented until #4073 is fixed.

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.