-
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
Don't persist keys for embedded entities #16779
Conversation
0eaa5b2
to
d4d422b
Compare
This is ready for review now |
d4d422b
to
8f50ca5
Compare
8f50ca5
to
f0ad142
Compare
f0ad142
to
5a44a8a
Compare
@smitpatel Please review this when you are able |
array.Add(_database.GetDocumentSource(dependentEntry.EntityType).CreateDocument(dependentEntry)); | ||
var embeddedDocument = embeddedDocumentSource.GetCurrentDocument(embeddedEntry); | ||
embeddedDocument = embeddedDocument != null | ||
? embeddedDocumentSource.UpdateDocument(embeddedDocument, embeddedEntry) ?? embeddedDocument |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why this uses coalesce but reference navigation is not using?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need to add all entities to the collection in order even if they weren't updated
The store JObject is now stored in a shadow property for embedded entities as well to allow to keep unmapped properties.
Fixes #13578
Part of #12086