There's no way to introspect on the parameter names.
So your choices become:
@Select({"SELECT * FROM send LIMIT #{1}, #{2}"})
List getAllItems(int offset, int limit);
...Or...
@Select({"SELECT * FROM send LIMIT #{offset}, #{limit}"})
List getAllItems(@Param("offset") int offset, @Param("limit") int limit);
Both suck. But we'll probably default to the first, and allow for the
second.
Gross.
Clinton
On Sun, Oct 4, 2009 at 8:00 PM, Guy Rouillier <[email protected]>wrote:
> I'd be curious to understand what the Java limitation is. I would have
> thought that with Java 1.5's support of varargs, limitations such as this
> would no longer exists. Of course, to use varargs here, I suppose we'd have
> to use Object[], which would shoot your type safety.
>
> Clinton Begin wrote:
>
>> It's a limitation in Java. However, we are working on a couple of
>> potential options. But it's not possible to do it the way you've written it
>> (which is really sad, because it's perfectly possible in C# and other
>> languages).
>>
>> Clinton
>>
>> 2009/10/4 Tomáš Procházka <[email protected] <mailto:
>> [email protected]>>
>>
>>
>> Why not supported this?
>>
>> @Select({"SELECT * FROM send LIMIT #{offset}, #{limit}"})
>> List getAllItems(int offset, int limit);
>>
>>
>> Its limitation of Java or bug in actual version?
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> <mailto:[email protected]>
>> For additional commands, e-mail: [email protected]
>> <mailto:[email protected]>
>>
>>
>>
>
> --
> Guy Rouillier
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
