Re: Avoiding N+1 selects with more complex graphs

case. > >On 6/23/05, Aaron Craven <[EMAIL PROTECTED]> wrote: >> >> Wonderful! >> >> So, using the example below, I would simply add a groupBy to my resultMap >> for Customer (say groupBy="customerID"), and one to my resultMap for Contact >>

Re: Avoiding N+1 selects with more complex graphs

00 >There's no limit. You can go as wide or deep as you like. You can load any >graph of practical limit (i.e. ridiculous graphs won't likely perform well). >But certainly this is possible. The unit test actually uses a three tier >nesting. > >Cheers, >Clinto

Re: Avoiding N+1 selects with more complex graphs

using the groupBy attribute. > >If you are not in a great big hurry, I will be looking at this in a >couple of days (possibly this weekend). > >Larry > > >On 6/22/05, Aaron Craven <[EMAIL PROTECTED]> wrote: >> >> I cannot decide if I've missed something i

Avoiding N+1 selects with more complex graphs

I cannot decide if I’ve missed something in the documentation, or if I’m just plain old confused, but either way I need some help. With iBATIS 2, I realize the N+1 selects problem has been solved by the addition of the groupBy property. However, I’m a bit confused as to how this would be done