Package liquibase.change.custom
Interface CustomTaskChange
- All Superinterfaces:
CustomChange
Interface to implement when creating a custom change that does not actually generate SQL.
If you are updating a database through SQL, implementing CustomSqlChange is preferred because the SQL can either be executed
directly or saved to a text file for later use depending on the migration mode used.
To allow the change to be rolled back, also implement the CustomTaskRollback interface.
If your change requires sql-based logic and non-sql-based logic, it is best to create a changeset that contains a mix of CustomSqlChange and CustomTaskChange calls.
- See Also:
-
Method Summary
Methods inherited from interface liquibase.change.custom.CustomChange
getConfirmationMessage, setFileOpener, setUp, validate
-
Method Details
-
execute
Runs the change logic for this custom change.- Parameters:
database
- the target database to apply the change to- Throws:
CustomChangeException
- if an exception occurs while processing the change
-