Overview
Liquibase recommends using the standard rollback functionality which “rewinds” a database to a specified point. All changesets deployed after that point are rolled back. These rollbacks are documented here:
...
However, there is a newly supported command hammer <dbdef> precise command which allows the user to selectively rollback specific changesets.
WARNING! With this command Liquibase cannot guarantee that database dependencies will not be impacted by the rollback
...
.
Take care not to remove changesets that later deployments built on.
For example:
Deploy a create table
Deploy a view on that table
If you now attempt to roll back only the changeset that created the table, then the view becomes invalid. It is up to the user to ensure that precise rollbacks include all the necessary database dependencies.
...