this post was submitted on 11 Feb 2024
41 points (93.6% liked)
Programming
17426 readers
49 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities [email protected]
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Yeah, the post on Reddit had some insightful comments as well.
I did not think of nested objects that may be returned by an entity framework before.
EF can have big problems with "Cartesian explosions" if an object has two lists of sub objects to return, it will get listA length x listB length items due to how the joins work. You can see how this leads to the explosion part of the name (with more objects or lists).
Their solution is a "split query" option, that does each sub table as a separate query, then seamlessly gives you the combined result.
If a change like this let's you get those different table lists as distinct lists with the processing and round trip time of multiple requests then it could be a game changer.
(Source - my last week ๐คฃ๐ญ + lots of EF docs)