It will fetch part of it unfortunately... so the general rule of thumb is: Don't mix offset/limit with join mapping (nested result maps). There is no easy way to solve this in a SQL mapper like iBATIS. It's far easier with a true ORM, as they can do two queries, one for the parent IDs, and then use an IN clause to get the objects. You could implement it that way with iBATIS as well, but there's nothing iBATIS can do automatically for you.
Clinton On Tue, Sep 29, 2009 at 5:10 PM, John Seer <pulsph...@yahoo.com> wrote: > > Hello, > > I am little bit confused in how Scrollable results are working for ibatis, > the row num we pass in, is it going to fetch full object or it will not > fetch some part of it? > > > Regards > -- > View this message in context: > http://www.nabble.com/Scrollable-result-Set-tp25672496p25672496.html > Sent from the iBATIS - User - Java mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-java-unsubscr...@ibatis.apache.org > For additional commands, e-mail: user-java-h...@ibatis.apache.org > >
