Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Never do a many-to-many, m:m merge. Address comments on E05 #86

Open
andrasvereckei opened this issue Aug 18, 2020 · 1 comment
Open

Never do a many-to-many, m:m merge. Address comments on E05 #86

andrasvereckei opened this issue Aug 18, 2020 · 1 comment

Comments

@andrasvereckei
Copy link
Contributor

I would suggest to qualify the 'Never do a many-to-many, m:m merge.' statement by writing that many-to-many relationships are hardly encountered and that the student should be well aware of its applicability in their particular use-case.
@sergiocorreia
Copy link

TBH, for many-to-many relationships (cartesian products) then joinby is the way to go. I've never seen a piece of code where m:m merges are the way to go, and I've seen several where it was used by mistake.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@sergiocorreia @andrasvereckei