Hibernate and MySQL issues with BOOLEAN/BIT

talibksm · **Joined:** Thu Oct 27, 2005 10:06 am **Posts:** 1

Hibernate version: 3.1

All,

I've run into an issue that I've seen posted here, but I haven't seen a resolution for it.

Per MySQL's documentation, http://dev.mysql.com/doc/refman/5.0/en/ ... rview.html, MySQL 5.0.3 no longer converts a BIT to a TINYINT(1). That's problematic because the Hibernate MySQLDialect converts BOOLEAN to BIT, which was proper prior to MySQL 5.0.3.

The issue has caused problems in my deployment of JBoss Portal. I've fixed the issue by inserting the Portal tables by hand using answers from the great oracle Google. However, I'm still wondering if this is an issue that is going to be addressed in a future version of Hibernate. I would suggest just converting the BOOLEAN to TINYINT(1) in the MySQLDialect. That should remedy the problem for most current versions of MySQL.

I'm a Hibernate newbie, so if there's a way that I can change something on my end to make this happen automatically, I would love to learn how to do that.

Thanks,
Talib

genekhart · **Joined:** Thu Jun 23, 2005 4:11 pm **Posts:** 24

The way I worked around is the following:

<property name="name" type="boolean">
<column name="name" sql-type="tinyint" not-null="true"/>
</property>

fizzy · **Joined:** Sun Dec 14, 2003 10:47 am **Posts:** 23

We have this same issue. We use xdoclet to create out .hbm.xml files. We support several databases and do several schema mods depending on the db. We accomplish this by post processing the .hbml.xml files. In this case we simply map all the boolean types to sql-type="tinyint"...

I am wondering if creating a Mysql5Dialect would fix the problem. We have created customer dalects before and it isn't that hard to do. Particularly in this case simply extend mysqldialect and override the single behaviour...

When/if I try creating a mysql5dialect I will post here the results...

fizzy · **Joined:** Sun Dec 14, 2003 10:47 am **Posts:** 23

Well I looked at the MysqlDialect... Noticed for the first time an Innodb and a MyIsam dialect which is good to know since for some things Mysql behaves quite differently depending on the table type...

I couldn't find a simple way to do this in the dialect... So I am simply using hte post processing step I mentioned before where we just add a column tag to all boolean...

<column name='xyz' sql-type='tinyint' not-null='true' />

For Boolean (non-primitve) we add this

<column name='xyz' sql-type='tinyint' not-null='false' />