Thanks for your response Steve,
The reason for doing this is that I'm migrating a legacy application to Liquibase, and it would be convenient if I could build the entire database from liquibase, rather than using multiple tools. The main benefit Liquibase gives me is versioning with changesets, and running an import from another tool won't easily fit into the changset model.
Currently my legacy application has many unmanaged and unversioned database snapshots, which makes it very difficult to run repeatable CI cycles of: develop, build, test, release, deploy.
Like you say, there are more efficient ways to load large datasets, and I may need to take that approach instead.
The reason for doing this is that I'm migrating a legacy application to Liquibase, and it would be convenient if I could build the entire database from liquibase, rather than using multiple tools. The main benefit Liquibase gives me is versioning with changesets, and running an import from another tool won't easily fit into the changset model.
Currently my legacy application has many unmanaged and unversioned database snapshots, which makes it very difficult to run repeatable CI cycles of: develop, build, test, release, deploy.
Like you say, there are more efficient ways to load large datasets, and I may need to take that approach instead.