Updating limitations of owned entity types #770
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Fixes #764 and applies minor 2.1 updates.
ajcvickers
approved these changes
Jun 14, 2018
| - Since they use table splitting by default owned types also have the following restrictions unless explicitly mapped to a different table: | ||
| - They cannot be owned by a derived type | ||
| - The defining navigation property cannot be set to null (i.e. owned types on the same table are always required) | ||
| - Inheritance hierarchies of owned entity types are not supported |
There was a problem hiding this comment.
"Inheritance hierarchies that include owned entity types"?
AndriySvyryd
approved these changes
Jun 14, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #764 and applies minor 2.1 updates.