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 change set that contains a mix of CustomSqlChange and CustomTaskChange calls.
Definition at line 17 of file CustomTaskChange.java.
Public Member Functions | |
| void | execute (Database database) throws CustomChangeException, UnsupportedChangeException |
| Method called to run the change logic. | |
| void liquibase.change.custom.CustomTaskChange.execute | ( | Database | database | ) | throws CustomChangeException, UnsupportedChangeException |
Method called to run the change logic.
| database |
| liquibase.exception.CustomChangeException | an exception occurs while processing this change | |
| liquibase.exception.UnsupportedChangeException | if this change is not supported by the liquibase.database.Database passed as argument |