No, I meant I almost never have a parameterClass or parameterMap in my mapped statements.
I use Map objects a lot for reads, but not often for writes. Larry On Mon, Dec 15, 2008 at 7:38 AM, Rick <[email protected]> wrote: > On Sun, Dec 14, 2008 at 11:02 AM, Larry Meadors <[email protected]> > wrote: >> On Sat, Dec 13, 2008 at 8:09 PM, Clinton Begin <[email protected]> >> wrote: >>> That said, (to further argue with myself), I actually prefer the flexibility >>> of not typing the statement. It's a sort of duck typing for iBATIS. >>> >> >> I almost never use a parameter type or map. :-/ >> >> I'm just lazy that way. >> > > Even for retrieves? I like using map as my parameter object for > retrieves. I always seem to run into cases where the POJO itself > doesn't really fit for retrieves because you often need extra > parameters that I don't feel like sticking in as properties on my > pojo. Maps seem to work nice for this. ( Sometimes I'll create a > FooBarSearchCriteria object, if it's parameters chosen from a > front-end, but often a Map is just fine.) > > Don't fear the Map! </vic> >
