Hello Michael,

Thanks for the hint. That might be a relict from the time when I
wasn't sure about integrating typesafety with respect to the bound of
<T>. The type T is certainly useful when reading data, but in
principle, most RDBMS use implicit casts / conversions when types
don't match. I.e. it's perfectly OK to write things like

SELECT * FROM my_table WHERE '1' = 1

But it is inconsistent with the overall API, so probably you're
right... I have opened ticket
https://sourceforge.net/apps/trac/jooq/ticket/835

Cheers
Lukas

PS: I'm posting this to the user group, too, as this is an
incompatible change that might affect other users, not just jOOQ
developers

2011/9/14 Michael <[email protected]>:
> The declaration of the method set in the interface InsertSetStep
> should be
>  <T> InsertSetMoreStep set(Field<T> field, T value);
> to be typesave.

Reply via email to