Adding model for Many to Many scenarios #20491
Merged
Conversation
This file contains hidden or 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
maumar
commented
Apr 1, 2020
| .HasMany(e => e.SelfSharedEntityLeftWithPayload) | ||
| .WithMany(e => e.SelfSharedEntityRightWithPayload) | ||
| .UsingEntity<OneSelfSharedEntityWithPayload>( | ||
| r => r.HasOne(x => x.Right).WithMany().OnDelete(DeleteBehavior.NoAction), |
There was a problem hiding this comment.
@AndriySvyryd is this how we should configure self many to many? (i.e. the OnDelete part)
maumar
force-pushed
the
many_to_many_model
branch
2 times, most recently
from
2ff7693 to
6d36cbd
Compare
AndriySvyryd
reviewed
Apr 1, 2020
| namespace Microsoft.EntityFrameworkCore.TestModels.ManyToManyModel | ||
| { | ||
| // TODO: remove and use shared entity instead | ||
| public class OneToTwoSharedEntity |
There was a problem hiding this comment.
It's shared type, not shared entity
AndriySvyryd
approved these changes
Apr 1, 2020
Entities: One, Two, Three - regular CompositeKey - entity with composite key Root, Branch, Leaf - inheritance Navigations (all many to many have corresponding navigation on the other side that is not listed here): One - TwoFullySpecified - ThreeFullySpecifiedWithPayload - TwoSharedType - ThreeSharedType - SelfSharedTypeWithPayload - BranchFullySpecified Two - ThreeFullySpecified - SelfFullySpecified - CompositeSharedType Three - CompositeFullySpecified - RootSharedType Composite - RootSharedType - LeafSharedType For now shared type scenarios are not supported in metadata API so we added linking entities temporarily. Those should be removed once the support is in.
maumar
force-pushed
the
many_to_many_model
branch
from
6d36cbd to
2aaaa35
Compare
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
Entities:
One, Two, Three - regular
CompositeKey - entity with composite key
Root, Branch, Leaf - inheritance
Navigations (all many to many have corresponding navigation on the other side that is not listed here):
One
Two
Three
Composite
For now shared entity scenarios are not supported in metadata API so we added linking entities temporarily. Those should be removed once the support is in.