Package liquibase.change

The change package contains the available database "changes".

See: Description

Interface Summary

Interface	Description
Change	Interface all changes (refactorings) implement.
ChangeWithColumns<T extends ColumnConfig>	Markers a Change class as containing one or more ColumnConfig configuration.
DbmsTargetedChange	Adding 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
AbstractChange	Standard superclass to simplify Change implementations.
AbstractSQLChange	A common parent for all raw SQL related changes regardless of where the sql was sourced from.
AbstractSQLChange.NormalizingStream
AbstractTableChange
AddColumnConfig
ChangeFactory	Factory class for constructing the correct liquibase.change.Change implementation based on a command name.
ChangeMetaData	Static metadata about a link Change.
ChangeParameterMetaData	Static metadata about a Change parameter.
ChangeStatus
CheckSum	CheckSums are used by liquibase to determine if a Change has been modified since it was originally ran.
ColumnConfig	The standard configuration used by Change classes to represent a column.
ColumnConfig.ValueNumeric
ConstraintsConfig	The standard configuration used by Change classes to represent a constraints on a column.

Enum Summary

Enum	Description
ChangeStatus.Status

Annotation Types Summary

Annotation Type	Description
DatabaseChange	Annotation used by AbstractChange to declare ChangeMetaData information.
DatabaseChangeNote
DatabaseChangeProperty	Annotation used by AbstractChange to declare ChangeParameterMetaData information.

Package liquibase.change Description

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 Change implementations and including them in the classpath.

See Also:

http://liquibase.org/extensions