'generateChangeLog' produces changelog which cannot be deployed using 'update'
Description
given a table in a mysql schema: create table XXX ( id bigint not null auto_increment, activation_date datetime, enabled boolean not null ); running generateChangeLog will produce a changelog like this: <createTable catalogName="YYY" tableName="XXX"> <column autoIncrement="true" name="id" type="BIGINT(19)"> <constraints primaryKey="true"/> </column> <column name="activation_date" type="datetime(19)"/> <column name="enabled" type="BIT"> </createTable>
when I run update with the changelog on the same db and clean schema I've got following problems: 1) datetime(19) cannot be created on MySql (so I have to replace it to datetime) 2) after fixing manually the datetime problem I've got a table, which is different from the orginal one: instead of column 'enabled boolean not null' it will produce column 'enabled bit not null', which makes a difference!
given a table in a mysql schema:
create table XXX (
id bigint not null auto_increment,
activation_date datetime,
enabled boolean not null
);
running generateChangeLog will produce a changelog like this:
<createTable catalogName="YYY" tableName="XXX">
<column autoIncrement="true" name="id" type="BIGINT(19)">
<constraints primaryKey="true"/>
</column>
<column name="activation_date" type="datetime(19)"/>
<column name="enabled" type="BIT">
</createTable>
when I run update with the changelog on the same db and clean schema I've got following problems:
1) datetime(19) cannot be created on MySql (so I have to replace it to datetime)
2) after fixing manually the datetime problem I've got a table, which is different from the orginal one: instead of column 'enabled boolean not null' it will produce column 'enabled bit not null', which makes a difference!