Reputation: 31
I would like to use liquibase for db versioning.
I face a kind of problem. I would like to know how to do for commiting changes I make directly on the database to the db.changelog.xml.
I tried the command generateChangeLog but it append the script to create the complete database one after the other. I would like to have only the changes between an old db.changelog.xml and the database.
I saw that people use a reference database, I find that very heavy and not very flexible and scalable for doing a good continuous integration.
Is there any other solution to simply compare the differences bewteen a db.changelog.xml and a database and write them in this db.changelog.xml ?
Thanks.
Upvotes: 1
Views: 469
Reputation: 6383
I guess that is not how liquibase is intended to be used. You should do all your changes through liquibase changesets and let liquibase handle db updates. If you additionally also change the db manually it will get tough to handle this.
There is no real support for this in liquibase (imho).
You can only try to come up with a solution yourself by using the generateChangeLog
command and then compare the result to an existing other changelog file.
I think the intention of the generateChangeLog
is to use it at the start of a project when you already have an existing db and you want to switch over to use liquibase. But not to constantly use this to overcome manual changes that have been done without liquibase.
Upvotes: 1