Hi Eric,
You're right, it looks as though the compiler prefers the Field.in(T...)
method over the Field.in(Collection<?>) method signature, when T binds to
Object.
However, I cannot reproduce this particular test case, neither with your
code, nor with this one here:
@Test
public void testPlainSQLInPredicate() throws Exception {
List<String> v1 = Arrays.asList("1", "2");
Condition c1 = field("f").in(v1);
assertEquals("f in (?, ?)", r_ref().render(c1));
assertEquals("f in ('1', '2')", r_refI().render(c1));
Set<String> v2 = new TreeSet<String>(Arrays.asList("1", "2"));
Condition c2 = field("f").in(v2);
assertEquals("f in (?, ?)", r_ref().render(c2));
assertEquals("f in ('1', '2')", r_refI().render(c2));
}
What compiler are you using? javac, or Eclipse? What version? And what
version of jOOQ?
Cheers,
Lukas
2014-06-24 17:12 GMT+02:00 Eric Wadsworth <[email protected]>:
> It appears that this does work, if I use an array instead of a List:
>>
> String[] responseIds = {"id1", "id2", "id3"};
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "jOOQ User Group" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.
>
--
You received this message because you are subscribed to the Google Groups "jOOQ
User Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
