You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A Dictionary is overkill for a type that will only store two key properties, which is the common case for many-to-many with non-composite keys on either end. Instead, consider using:
Just out of curiosity, how is this proposal different from EntityTypeBuilder<TRightEntity> UsingEntity<TJoinEntity>(...)? I have scenarios where I map a simple entity to a many-to-many join table and that is already supported. I do, however, have to manually specify the left & right sides of the mapping entity's relationships, so is this about making that process automatic for Plain Old Data types?
A Dictionary is overkill for a type that will only store two key properties, which is the common case for many-to-many with non-composite keys on either end. Instead, consider using:
The text was updated successfully, but these errors were encountered: