-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrations: CHECK Required Columns on TPH Derived Types #2595
Milestone
Comments
rowanmiller
added
the
help wanted
This issue involves technologies where we are not experts. Expert help would be appreciated.
label
Jul 10, 2015
divega
added
good first issue
This issue should be relatively straightforward to fix.
help wanted
This issue involves technologies where we are not experts. Expert help would be appreciated.
and removed
help wanted
This issue involves technologies where we are not experts. Expert help would be appreciated.
good first issue
This issue should be relatively straightforward to fix.
labels
May 31, 2019
ajcvickers
added
good first issue
This issue should be relatively straightforward to fix.
and removed
help wanted
This issue involves technologies where we are not experts. Expert help would be appreciated.
labels
Aug 5, 2019
Clearing milestone to determine whether we want this to be in EF Core or in EFCore.CheckConstraints (efcore/EFCore.CheckConstraints#6) |
Also useful for optional dependents using table splitting |
63 tasks
A Stack Overflow question about this: EF Core saves null value of required property |
ajcvickers
removed
the
good first issue
This issue should be relatively straightforward to fix.
label
May 14, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For required properties on derived types, we could add a
CHECK
constraint to ensure it'sNOT NULL
when the discriminator is one that type or one of it's derived types.The text was updated successfully, but these errors were encountered: