Quick word of advice when dealing with deep parent/child reloationships:
Do not use lazy loading feature. That way lies madness.
Re:Net 9.0 LINQ Performance Improvements
by magicalhippo on Friday October 18, 2024 @05:54PM
(#41883854)
We're not doing that where we come from. All child tables have the main id so we can load the data for all child rows with just one query per child table, and we load everything at once.
We were planning on sticking with this, it has worked well so far, but good to know to avoid getting tempted by the alternative.
We're quite accustomed to writing our own SQL select statements and would like to continue doing that to have known performance, but the update, insert and delete statements are a chore to do manually, especially for once you're 4-5 parent child levels deep.