I don't know if phasing out parameter maps is such a good idea. Right now they are not very useful because you can't do the things I suggested, however if you could then when you use them and change a method name in your java bean you would only have to chage your parameter map and not every statement that uses the java class. I think they would be great if they could do these things. Right now I am having a hell of a time having to update all my insert and update statements when the java beans change.
Kris
Clinton Begin <[EMAIL PROTECTED]> wrote:
Clinton Begin <[EMAIL PROTECTED]> wrote:
Both are good suggestions (please add them to JIRA).
The reason behind why there hasn't been much development or evolution
around Parameter Maps is twofold:
1) They're a lot simpler than result maps, and require less configuration.
2) Very few people use theelement. You can do
everything with inline parameters now (#prop,attr1=val1,att2=val2#
etc.).
I'm dreaming of a day when both theand
elements disappear!
Cheers,
Clinton
On Thu, 3 Feb 2005 18:34:55 -0800 (PST), Kris Rasmussen
<[EMAIL PROTECTED]>wrote:
> Why can you extends a result map but not a parameter map? Also, why can't
> you map a parameter in a parameter map to a specific database column so that
> order doesn't matter. This would allow you to do things like define a
> paramter map for an entire class and then only select the parts that are
> required for the specific statement you are interested in.
>
> Kris
>
> ________________________________
> Do you Yahoo!?
> Yahoo! Search presents - Jib Jab's 'Second Term'
>
>
Do you Yahoo!?
Yahoo! Search presents - Jib Jab's 'Second Term'