I’ve read about how you can generate changelog.xml from an existing schema. That’s fine, but I have existing systems that I don’t want to touch, except to bring in new changes. I also have completely new systems which require all changes be applied.
So, I want to get liquibase to only perform migrations from changeset X when running on an existing system. I.e. that system’s DB is at revision X-1 (but no liquibase sys tables), and I don’t want any preceeding migrations applied.
Many thanks,
Pat
I think the easiest would be to execute the initial setup on an empty database at first and export the entry(ies) liquibase does insert into the
DATABASECHANGELOGtable. Then I’d export these entries and insert them manually into one of the target databases into theirDATABASECHANGELOGtable, so liquibase does not execute the “change” there again.Of course I’d test all that with test dumps on a test machine… 🙂