The change package contains the available database "changes". "Change" was chosen as a term over "refactoring" because refactoring should technically result in the same functionality whereas the database changes do affect functionality. Liquibase ships with a set of changes that range from low-level create table style changes to higher level "introduce lookup table" style changes, but additional custom changes can be added via by creating new
Changeimplementations and including them in the classpath.
- See Also:
Interface Summary Interface Description ChangeInterface all changes (refactorings) implement. ChangeWithColumns<T extends ColumnConfig>Markers a Change class as containing one or more
DbmsTargetedChangeAdding this interface to your Change class allows you to specify a dbms attribute listing the databases the change is applied to.
Class Summary Class Description AbstractChangeStandard superclass to simplify
AbstractSQLChangeA common parent for all raw SQL related changes regardless of where the sql was sourced from. AbstractSQLChange.NormalizingStream AbstractTableChange AddColumnConfig ChangeFactoryFactory class for constructing the correct liquibase.change.Change implementation based on a command name. ChangeMetaDataStatic metadata about a
ChangeParameterMetaDataStatic metadata about a
ChangeStatus CheckSumCheckSums are used by liquibase to determine if a Change has been modified since it was originally ran. ColumnConfigThe standard configuration used by Change classes to represent a column. ColumnConfig.ValueNumeric ConstraintsConfigThe standard configuration used by Change classes to represent a constraints on a column. NormalizingStreamV8 Deprecated.
Enum Summary Enum Description ChangeStatus.Status
Annotation Types Summary Annotation Type Description DatabaseChange DatabaseChangeNote DatabaseChangePropertiesContainer object which allows multiple
DatabaseChangePropertyannotations to be used on a single property.