I've branched at https://github.com/carljoans/liquibase
These are special considerations for MySQL which include the following:
-- Fulltext Index for columns
-- SQL escape. Escaping single quotes when generating csv data dump.
-- Table Engine. MyISAM, InnoDB, etc. added to changlelog
-- Column Datatype replicated exactly as created. ( i.e. int only went up to int(10) even though the column was created as int(11), double created as double(22) which generates an sql error, etc. )
Then there are some general changes that I just thought would be helpful to my specific projects:
-- only create csv during data dump if there is data in table, instead of generating a csv for an empty table.
-- Creating multiple changelog files at once
-- Including or Excluding only certain tables in data or creation dump. Say if you want to export only specific tables. As per the previous point, you can put certain tables in one changelog and others in another and also ignore others completely. Useful if you have test tables or code generated tables you don't want to include in your releases.
Some of the groovy tests need to be edited, .i.e remove some of the test cases, when building to ignore the changes. Or add the changes to the groovy tests where applicable.
These are special considerations for MySQL which include the following:
-- Fulltext Index for columns
-- SQL escape. Escaping single quotes when generating csv data dump.
-- Table Engine. MyISAM, InnoDB, etc. added to changlelog
-- Column Datatype replicated exactly as created. ( i.e. int only went up to int(10) even though the column was created as int(11), double created as double(22) which generates an sql error, etc. )
Then there are some general changes that I just thought would be helpful to my specific projects:
-- only create csv during data dump if there is data in table, instead of generating a csv for an empty table.
-- Creating multiple changelog files at once
-- Including or Excluding only certain tables in data or creation dump. Say if you want to export only specific tables. As per the previous point, you can put certain tables in one changelog and others in another and also ignore others completely. Useful if you have test tables or code generated tables you don't want to include in your releases.
Some of the groovy tests need to be edited, .i.e remove some of the test cases, when building to ignore the changes. Or add the changes to the groovy tests where applicable.