scaffolding: CHECK CONSTRAINT cannot be scaffolded
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
No source file or test is named. Start by tracing how database CHECK constraints are represented in scaffolding metadata and how that metadata becomes generated entity configuration; compare the reported output with the expected HasCheckConstraint form. Done means scaffolded output preserves the constraint name and expression so recreating the database includes the CHECK constraint.
Written by the indexing model from the issue text.
Description
EF Core supports defining check constraints when working code-first, but there is nothing in the scaffolding metadata that allows us to define this when generating code from the database. This means that when a database with existing CHECK constraints is scaffolded and the output is used to generate a new database, the CHECK constraints will not be included in the new database.
Script:
CONSTRAINT Chk_Languages_Lyrics_Length_Equal CHECK (ARRAY_LENGTH(LyricsLanguages) = ARRAY_LENGTH(Lyrics))
Actual:
entity.HasAnnotation("CONSTRAINT `Chk_Languages_Lyrics_Length_Equal`", "CHECK ARRAY_LENGTH(LyricsLanguages) = ARRAY_LENGTH(Lyrics)");
Expected:
entity.HasCheckConstraint("Chk_Languages_Lyrics_Length_Equal", "ARRAY_LENGTH(LyricsLanguages) = ARRAY_LENGTH(Lyrics)");
- Dominant language
- C#
- Stars
- 34
- Forks
- 13
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 19
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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 googleapis/dotnet-spanner-entity-framework
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
googleapis/dotnet-spanner-entity-framework#775 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
googleapis/dotnet-spanner-entity-framework#777 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
googleapis/dotnet-spanner-entity-framework#767 ·
Maintainers usually reply within 1 day
-
priority: p2 samples type: bug
Difficulty 4/5 3-5 days Newbie friendliness 45/100
googleapis/dotnet-spanner-entity-framework#722 ·
Maintainers usually reply within 1 day
-
priority: p2 type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 50/100
googleapis/dotnet-spanner-entity-framework#712 ·
Maintainers usually reply within 1 day
All issues in googleapis/dotnet-spanner-entity-framework
Similar issues
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
KnifeLemon/Filee#294 ·
Maintainers usually reply within 1 day
-
応募に出す、展示スペースの図面を作るOpenmtg-decide submission
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Fialuxe/MouthOfGod_System#288 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
gavin-wolfe/wolfden#104 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
[BUG] Still libmicrohttpd dependency is not removed properly from External-Dependency-Info.txt filePossibly taken A pull request linked to this issue is open or already merged. Opentype/bug
Difficulty 1/5 Under an hour Newbie friendliness 72/100
Maintainers usually reply within 1 day