That's a good observation. Can you throw a feature request in jira?
Cheers,
Clinton
On 2010-03-05, François Schiettecatte wrote:
> Hi
>
> Any reason why there are only two select() methods in
> org.apache.ibatis.session:
>
> void select(String statement, Object p
Hi
Any reason why there are only two select() methods in org.apache.ibatis.session:
void select(String statement, Object parameter, ResultHandler handler);
void select(String statement, Object parameter, RowBounds rowBounds,
ResultHandler handler);
I would have expected to see this for
l of my iBatis configuration via annotations and need to
> perform a select with a ResultHandler.
>
> Using the AuthorMapper defined in the iBatis-3 Users Guide on page 54, how
> would I add a result handler to selectAut
iBatis 3.0-Beta-9 for Java.
I have done all of my iBatis configuration via annotations and need to
perform a select with a ResultHandler.
Using the AuthorMapper defined in the iBatis-3 Users Guide on page 54,
how would I add a result handler to selectAuthors()?
Paul Spencer
nja:
>> >>
>> >> Just to make sure I understand your reply for any future work. I don't
>> >> believe I am using a join mapper. I have a POJO that maps directly to
>> a
>> >> custom (yet extremely complicated) sql statement. The POJO
;> any
> >> collections, and is basically stand alone. It is my understanding from
> >> your
> >> code, that my type of POJO isn't going to utilize the join mapper
> method,
> >> since the next POJO will be unique.
> >>
> >> Clinton Begi
It is my understanding from
>> your
>> code, that my type of POJO isn't going to utilize the join mapper method,
>> since the next POJO will be unique.
>>
>> Clinton Begin wrote:
>> >
>> > The difference between RowHandler and ResultHandler i
y stand alone. It is my understanding from
> your
> code, that my type of POJO isn't going to utilize the join mapper method,
> since the next POJO will be unique.
>
> Clinton Begin wrote:
> >
> > The difference between RowHandler and ResultHandler is only in name.
&g
ton Begin wrote:
>
> The difference between RowHandler and ResultHandler is only in name. They
> did the same thing.
> I'd be interested to know if iBATIS 2.x works for you in this regard. As
> far
> as I can recall, 2.x had the same design if you invoked the join mapper...
The difference between RowHandler and ResultHandler is only in name. They
did the same thing.
I'd be interested to know if iBATIS 2.x works for you in this regard. As far
as I can recall, 2.x had the same design if you invoked the join mapper...
See, as soon as you try to use a JOIN to l
understanding that in Ibatis 3 that the ResultHandler has replaced the
RowHandler. Was there a specific design decision made not to allow a row by
row walk through?
As a work around I was looking into the Plugin feature. It looks like I can
Intercept the resultSetsHandler method, and write my own
to
> process one line at a time and not have the nestedResultObjects store each
> object?
>
> My goal:
> * Grab a row
> * Send it to be processed
> * Once processed, move on to the next row.
> Note: Once a row is processed I no longer need a tie back to the object.
>
>
tie back to the object.
I have included the custom ResultHandler, the unit test and the
configuration file. Please let me know if you need other information.
package com.primetherapeutics.benplanmgr.entity.rxclaim;
import org.apache.ibatis.executor.result.ResultContext;
import
13 matches
Mail list logo
