I am currently switching from PostgreSQL to MySQL .. I know I know.. but I'm facing the same issue XD
I'm just going to create another converter for that type unless there is a simpler solution by now :) BR; Stefan On Wednesday, 16 November 2011 00:07:58 UTC+1, Lukas Eder wrote: > > Hello Juan, > > 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 <[email protected] <javascript:>>: > > well, tinyint(1) gets converted to Byte too. After all bool, boolean are > > synonyms to tinyint(1) in mysql > > > > > > 2011/11/15 Juan Miguel Cejuela <[email protected] <javascript:>> > >> > >> Hi there, > >> > >> using MySQL 5.5.15 my columns with type BOOL or BOOLEAN get converted > into > >> Byte. > >> > >> Is this normal or is this a bug? Workaround now is tinyint(1) ? > >> > >> > >> Thanks, //keep the amazing good work Lukas > >> > >> > >> > >> -- > >> Juan Miguel Cejuela > >> [email protected] <javascript:> > >> jmcejuela.com > >> +49 176 627 581 05 > >> > > > > > > > > -- > > Juan Miguel Cejuela > > [email protected] <javascript:> > > jmcejuela.com > > +49 176 627 581 05 > > > > > > -- 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.
