D'oh, I forgot to change those. I was using parameterClass before and just
modified to parameterMap to use the typehandler.
Thanks again! I will after implementing Jeff's solution.
Clinton Begin wrote:
>
> LOL good catch Jeff... I didn't even notice that.
>
> FWIW: iBATIS 3 resolves this i
Thanks Jeff! Is this solution that you provided for skipping parameterMap
going to work with 2.3.3 only or would it work for earlier versions as well?
Jeff Butler-2 wrote:
>
> If you use a , then you must use question marks as markers
> in
> your statement. I suggest you skip the parameter ma
We are trying to resolve some N+1 query situations in our application, and
are finding a couple of features of our appliation that seem to limit our
ability to use the "groupBy" solution. I'm wondering if there are aspects of
the issues we aren't seeing.
The problems are these:
1. In places where
LOL good catch Jeff... I didn't even notice that.
FWIW: iBATIS 3 resolves this inconsistency. No more question marks
anywhere... :-)
Clinton
On Tue, Sep 2, 2008 at 11:45 AM, Jeff Butler <[EMAIL PROTECTED]> wrote:
> If you use a , then you must use question marks as markers in
> your statement
If you use a , then you must use question marks as markers in
your statement. I suggest you skip the parameter map completely and specify
the type handler in the statement:
#keyList[],handler=com.jrapp.ibatis.KeyHandlerCallback#
BTW - declared parameter maps will likely go away with iBATIS 3 - w
Clinton this does not seem to work. Any other ideas? Any other way around to
handle this?
Thanks!
Clinton Begin wrote:
>
> Upgrade to 2.3.3
>
> Cheers,
> Clinton
>
> On Thu, Aug 28, 2008 at 5:00 PM, J R <[EMAIL PROTECTED]> wrote:
>
>>
>> I have a parameterClass which holds List and a Long,
