MySQL 4.1 uses TINYINT for Boolean type, but MySQL 5.0 use Bit(1). After upgrading to MySQL 5.0 and all mapping tables have been re-created.

I got

Data too long for column "read" that is a boolean type.

when inserting a row.

How to solve this problem? Thanks.

I'm having the same problem, did you find an solution?

No. back to MySQL 4.1

The easiest, and most reliable method, would be to do the update yourself...

First you add an extra bit column
Then you update the values so that:
update mytable set bitvalue=1 where tinyintcolumn = 1
update mytable set bitvalue=0 where tinyintcolumn = 0
update mytable set bitvalue=null where tinyintcolumn is null
Now you delete the tinyintcolumn
Rename bitcolumn to tinyintcolumn

Done.

take a look at http://opensource2.atlassian.com/projec ... se/HHH-468 for a discussion of the subject.

The thread is geared towards those using hbm files, so if you are using annotations, you can use the @Column annotation with the
"columnDefinition" attribute set to "BOOLEAN" to get around this. The newer MySQL JDBC driver then silently converts this to tinyint(1) for you and you are back to the behavior as under MySQL 4.x

For example:



I've tested this with MySQL ConnectorJ 3.1.12 and MySQL 5.0.18 and my DDL generates correctly (i.e. tinyint(1) is back)

BTW, maybe someone on the Hibernate team could add an example like this to the documentation and/or unit test code?

The unit tests that come with annotations do not have an example of @Column using the "columnDefinition" attribute and the documentation just says "(6) columnDefinition (optional): override the sql DDL fragment for this particular column (non portable)" which is not exactly clear on what you should do.

Even better, a cross-reference document for moving from hbm to annotations would be really slick, something like:

Defining the database type:
HBM: uses the "sql-type" attribute
Annotations: uses the "columnDefinition" attribute of @Column

Defining the hibernate type:
HBM: uses the "type" attribute
Annotations: uses the "type" attribute of @Type

There are examples in the unit test suite

I see now... a file search using Win32's built in search did not find any mention of "columnDefinition" but when I used grep in cygwin, I found some examples:



Thanks! BTW, great job on the annotations package - they are working out very well for us.

thanks :-)

Bit(1) is better than TINYINT for boolean type. The table schema is generated using Bit(1). I do not understand why it complains too long when inserting records.

I have many entities, and lots of Boolean type columns. Using columnDefinition is not a good idea because it is not portable.
Hibernate should have a nicer way to solve this. Has Hibernate tested on MySQL 5.0.18?

Thanks!

Yes I test on MySQL 5
This is not Hibernate's responsibility if MySQL decide to break their client's applications.

Why is it MySql problem?
The mapping is done by Hibernate, and SQL dialect is generated by Hibernate.

After installed MySQL 5, I removed all tables from database, and recompile web application, and re-deploy it. Everything is fine until an entity with Boolean properties is persisted.