You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user-java@ibatis.apache.org by pu...@jpmchase.com on 2005/05/04 16:56:10 UTC
URGENT: Java: 1:M and N:M For SQL Maps - Avoiding N+1 Selects (1:M and M:N) -
Complex Collection Properties
Hello:
We are trying to implement a solution using iBATIS and would like to know
1. If there is a way around the N+1 Select issue for 1:M and M:N
relationships - the result would be populating Complex Collections
2. Could you please point me to documentation that talks about the
solution
3. If there is no workaround, what is the timeframe for including the
feature?
Please respond ASAP - we are stuck in the middle of an extremely URGENT
project.
Thank you very much for your help.
Best Regards,
Puneet Mehta
Re: URGENT: Java: 1:M and N:M For SQL Maps - Avoiding N+1 Selects (1:M and M:N) - Complex Collection Properties
Posted by Brandon Goodin <br...@gmail.com>.
>From our wiki:
http://opensource.atlassian.com/confluence/oss/display/IBATIS/How+do+I+get+around+the+N+Plus+1+selects+problem%3F
On 5/4/05, puneet.x.mehta@jpmchase.com <pu...@jpmchase.com> wrote:
>
> Hello:
>
> We are trying to implement a solution using iBATIS and would like to know
>
> 1. If there is a way around the N+1 Select issue for 1:M and M:N
> relationships - the result would be populating Complex Collections
> 2. Could you please point me to documentation that talks about the solution
> 3. If there is no workaround, what is the timeframe for including the
> feature?
>
> Please respond ASAP - we are stuck in the middle of an extremely URGENT
> project.
>
> Thank you very much for your help.
>
> Best Regards,
>
> Puneet Mehta
>