At the moment it's often wise to issue several AutoQueries where you'd otherwise query across 1:N relationships, in order to avoid an explosion in the number of rows returned in the result set. This then requires some many wire-up.
It would be much more awesome if Dapper.SimpleLoad could do this work for you: i.e., identify the 1:N relationships, and execute separate queries for each subset of objects, then wire them all up for you.
This is obviously quite a lot of work, but it would make life a lot easier for clients of the library, and would take the guesswork out of when/where to break things up yourself.
At the moment it's often wise to issue several AutoQueries where you'd otherwise query across 1:N relationships, in order to avoid an explosion in the number of rows returned in the result set. This then requires some many wire-up.
It would be much more awesome if Dapper.SimpleLoad could do this work for you: i.e., identify the 1:N relationships, and execute separate queries for each subset of objects, then wire them all up for you.
This is obviously quite a lot of work, but it would make life a lot easier for clients of the library, and would take the guesswork out of when/where to break things up yourself.