Re: Unconstrained signature interface mappers for ibatis 3

2009-08-30 Thread carlosjosepita
> It just requires a trivial modification in MapperMethod and a simple > mechanism to access positional parameters to get it working. For > example, MapperMethod could create a Map and put the first argument > under the key "first", the second one under "second", etc. That is, > positional access "

Re: Unconstrained signature interface mappers for ibatis 3

2009-08-30 Thread carlosjosepita
Hi Clinton, thanks for your detailed answer. I agree with you, although leaving aside the SQLUtils varargs proposal, I tend to priorize the unconstrained java mapper interface issue over the parameter naming issue, because (i) the interface defines a contract for the rest of the application

Re: Unconstrained signature interface mappers for ibatis 3

2009-08-30 Thread carlosjosepita
> I really wish Java made this easier. One thought I had to submit to the JCP > was to add introspection on parameter names by having the compiler > automatically create annotations for the parameter names. This was scheduled for java 6 but it was postponed, now it seems unlikely that java 7 will

Re: Unconstrained signature interface mappers for ibatis 3

2009-08-30 Thread carlosjosepita
> thoughts on the following two options: > > @Select("select * from employee where first_name = #{firstName} and > last_name = #{lastName}) > List findEmployeesLike(@Param("firstName") String firstName, > @Param("lastName") String lastName, @Offset int offset, @Limit, int limit); > > @Select("sel

Re: Unconstrained signature interface mappers for ibatis 3

2009-08-30 Thread carlosjosepita
> These mapper classes aren't meant to be DAOs... they're meant to be mappers. > If you like a DAO pattern, then you can still use it, with or without mapper Ok, I was thinking in dao terms and my perception was "mappers are almost daos... only if I had one more degree of freedom to define my inte

Re: Property/Field resolution order

2009-09-06 Thread carlosjosepita
I'm all for field access! Or a default field-then-property. I'm also fond of the syntax prop.(field) that you came out with time before in the list, but again reversing the default (prop).field. Best regards -- Carlos On Sun, Sep 06, 2009 at 01:23:18AM -0600, Clinton Begin wrote: > I'm almost sa

Re: Handling multiple table aliases in a query using one resultMap.

2009-09-07 Thread carlosjosepita
Sorry, I was just waiting for more feedback about the desirability of the prefix and property/field changes and I thought that you've filed a ticket for the other one. I can't create them just right so I'll do it tonight GMT-3 :). Best regards -- Carlos On Mon, Sep 07, 2009 at 08:28:25AM -0600, C