|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
It could be MySQL after all. Here's what I have found out:
There is a way to overcome this without using columnDefinition in the code - using a MySQL connection parameter.
You'd have to set transformedBitIsBoolean to true on the connection string. Because MySQL doesn't have a boolean datatype, Hibernate complains. Using the transformedBitIsBoolean parameter we can make the driver treat transformed BIT fields as Boolean. Transformed means however, it cannot actually be a BIT field, it has to be another field type silently transformed into BIT. That other field type is TINYINT(1).
So in order to get rid of column definitions we'd have to not only use the connection parameter, but also convert all the BIT fields into TINYINT(1), and the tinyInt1isBit flag has to be set to true (which it is by default).
http://dev.mysql.com/doc/refman/5.0/en/connector-j-reference-configuration-properties.html