You're right. MySQL doesn't really know a true boolean type:
http://dev.mysql.com/doc/refman/5.5/en/numeric-type-overview.html
It uses "bool" / "boolean" for compatibility reasons with other
databases, that support true booleans. See also this page:
http://dev.mysql.com/doc/refman/5.5/en/other-vendor-data-types.html
Currently, there is no custom type mapping in jOOQ, so your boolean
column is mapped to Byte. This reminds me that I should actually
implement a custom type mapping configuration in jooq-meta /
jooq-codegen:
https://sourceforge.net/apps/trac/jooq/ticket/947
Cheers
Lukas
2011/11/15 Juan Miguel Cejuela <jua...@jmcejuela.com>:
--
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 jooq-user+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Btw I am currently asking something on SO (again) http://stackoverflow.com/questions/37575716/java-lang-nullpointerexception-when-using-returning-fetchone