Hi Lukas, Thanks for your reply.
The problem with forcedType is that it maps SQL columns with a Java type. That means every time I create a column with a tinyint(1) type, I have to add this column in the forced type. I would like to tell jOOQ "I know what I am doing, always map tinyint with boolean whatever the column name". In my case I will round the problem since I am overriding the JavaGenerator anyway. Does a feature request on this will be accepted ? If so, I can do the work if you want (after I finished the cache layer :) Cheers, Aurélien On Friday, August 16, 2013 9:18:11 AM UTC+2, Lukas Eder wrote: > > Hi, > > Maybe this section will help? > http://www.jooq.org/doc/3.1/manual/code-generation/data-type-rewrites > > Cheers > Lukas > > > 2013/8/16 Aurélien Manteaux <[email protected] <javascript:>> > >> Hello, >> >> With MySQL the boolean type is synonym of the tinyint(1) type. >> As expected, jOOQ map the tinyint type with the java.lang.Byte type since >> a tinyint is stored in one bytes. >> >> However, since MySQL does not have a boolean type, I want in my project >> to use java.lang.Boolean instead of java.lang.Byte for the MySQL type >> tinyint. >> >> I know that there is a way to map a column with a Java type ( >> http://www.jooq.org/doc/3.0/manual/code-generation/codegen-advanced/), >> but is there a way to map a SQL type to a Java type ? >> >> Cheers, >> Aurélien >> >> -- >> 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] <javascript:>. >> For more options, visit https://groups.google.com/groups/opt_out. >> > > -- 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/groups/opt_out.
