Investigation: Nullable owned entity data preservation when moving between parents #36768
+41
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR investigates the reported issue where nullable owned entity data was allegedly being deleted when moving entities between parent collections in EF Core.
Investigation Results
After thorough investigation, the original issue described in #36206 does NOT reproduce in the current version of EF Core. The exact scenario from the issue description works correctly:
Key Findings
Testing
The current EF Core behavior correctly handles moving owned entities between parent collections while preserving their owned data, which is the expected and desired behavior.
Fixes #36206.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.