link-intersystems / dbunit-extensions Goto Github PK

Since flyway scripts are pure SQL they can insert data into the database. The migrated dataset should not contain the data that was inserted by flyway scripts. Thus lis-dbunit-migration needs to make a diff between the source and target db version.

The process should be:

1. Setup a clean database
2. Let flyway migrate to a source version
3. Save the database state of the source version
4. Insert the dataset that should be migrated
5. Migrate the dataset using flyway to the target version.
6. Export the target version as dataset
7. Make a diff between the target and source version
8. Export the changed dataset (the diff).

It would be nice if the database migraiton module can also migrate SQL scripts.

Here I have to check the limitations of SQL script migration. E.g. If a dataset SQL script contains more then just dml. There could be integration tests that use dml to simulate a schema change in order to test how the application handles such situations or how the error message look like.