Skip to content
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

Add nullability check to In-Memory Database #23094

Merged
merged 4 commits into from
Nov 9, 2020

Conversation

fagnercarvalho
Copy link
Contributor

Fixes #10613

@dnfadmin
Copy link

dnfadmin commented Oct 25, 2020

CLA assistant check
All CLA requirements met.

@ajcvickers ajcvickers self-assigned this Oct 26, 2020
Copy link
Member

@ajcvickers ajcvickers left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks great! Sorry for being so slow to review it.

@ajcvickers
Copy link
Member

@smitpatel @AndriySvyryd This looks good to me, but I'm not great at noticing places where style, etc. might be wrong. You guys are good at that. :-) Do you want to give it a quick scan?

@ajcvickers ajcvickers merged commit fbc43f6 into dotnet:main Nov 9, 2020
@ajcvickers
Copy link
Member

@fagnercarvalho Thanks for the contribution!

@devlear
Copy link

devlear commented Dec 8, 2021

I'm not sure if you would like a separate issue created for this, but the changed entity will still be in the ChangeTracker after the DbUpdateException is thrown.

@AndriySvyryd
Copy link
Member

@devlear That's by design. If any exception happens during SaveChanges EF tries to revert to the state before SaveChanges was called.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Validate requiredness (nullability) in the in-memory database
6 participants