liquibase treat tinyint(1) as boolean in mysql when using generateChangeLog

Going to have to push off looking into it more with 3.3 since there isn't a great clear answer at this point.

Further investigation: If I am using tinyInt1isBit=false for my jdbc connection url, "tinyInt1isBit" is a specifiic jdbc property, TINYINT(1) values from my local test database convert into TINYINT(3) by generateChangeLog command, but not into BIT(1) anymore. I thought this is a helpful thing at first, but then I run into problems if i want to migrate to hypersonic, for example, which does not support TINYINT(3) but BOOLEAN!

For short: It want to use BOOLEAN in my changesets which works in all of my cases. But for this, imho, the mentioned patch has to be applied, to convert BOOLEAN into TINYINT(1), in the case of a mysql database to avoid BIT(1). Last but not least this BIT value thing seems to be existing as of MySQL 5.0.3. Before 5.0.3, MySQL interprets BIT as TINYINT(1)? Thank you all for your ingeniousness!

Patch which provides a workaround and tries to help you understanding this issue. It maps liquibase booleans into MySQL's TINYINT(1) which is correct according to MySQL docs.

BIT(1) can be seen as BOOLEAN safely, or?

I am using int(1) now, to support default values which does not work with BIT(1) and BIT(1) is not recommended.

Really helpful would be a mapping what BOOLEAN stands for in liquibase imho (String can be an opportunity, too.)?

What do you think of a type mapping in a XML file, or else. BIT(1) can then be mapped into a liquibase type BOOLEAN and then back into TINYINT(1)/INT(1) or any other type!

The trouble I am running into is that when you create a column of type tinyint(1) and then ask the database what type it is, it returns "bit". It looks like there is a mysql setting of tinyInt1isBit that defaults to true, I'm not sure if the jdbc driver checks this or not.