[ http://nagoya.apache.org/jira/browse/IBATIS-27?page=comments#action_56752 ] Raymod Zhang commented on IBATIS-27: ------------------------------------
Wow, cool. Thanks Clinton! Looking forward to the new release! > N+1 Select statements > --------------------- > > Key: IBATIS-27 > URL: http://nagoya.apache.org/jira/browse/IBATIS-27 > Project: iBatis for Java > Type: Improvement > Components: SQL Maps > Versions: 2.0.8 > Reporter: Raymod Zhang > > This issue has been brought up a few time before. But since it is such an > important one, I have to post over here again to serve as a reminder. > Original post by Clinton in Sourceforge: > *******************BEGIN OF QUOTE*************************** > Amidst the many messages of the other two threads, this topic might have > become fuzzy. The other two threads were largely dealing with syntax and > schema changes to reduce the verbosity around joins that included duplicate > column names. > > This had nothing to do with the N+1 selects solution. > > iBATIS already has an N+1 solution for 1:1 relationships (nested bean prop > syntax w/join). It's very simple and not verbose at all. Duplicate column > names are easily resolved using SQL aliases. > > As for the N+1 solution for 1:M and M:N, these are documented thoroughly in > the Developer Guide. It clearly states in the developer guide that a solution > for this is coming. 2.0 was designed from the start to handle this and it > won't be a difficult change. > > Gilles and I have briefly discussed the XML stanzas and/or attributes that > we'll need to add for this. It's simply a matter of making a choice. The > community will be involved with making that choice. We'll hopefully get the > alternatives posted here soon. > **********************END OF QUOTE************************ > I am willing to help out if you guys need hands. Rather than waiting and > complaiting, I'm ok to do it myself :) But first thing I need to confirm is > the approach. Maybe clinton can enlighten me here. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://nagoya.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
