Package liquibase.change

package liquibase.change

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

Related Packages

Package	Description
liquibase	Liquibase top level namespace package.
liquibase.change.core	Technically, a Change expresses an intention for alter the structure of the Database.
liquibase.change.custom	Although Liquibase tries to provide a wide range of database refactorings, there are times you may want to create your own custom refactoring class.
liquibase.change.visitor

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
Change	Interface all changes (refactorings) implement.
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
ChangeStatus.Status
ChangeWithColumns<T extends ColumnConfig>	Markers a Change class as containing one or more ColumnConfig configuration.
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.
DatabaseChange	Annotation used by AbstractChange to declare ChangeMetaData information.
DatabaseChangeNote
DatabaseChangeProperties	Container object which allows multiple DatabaseChangeProperty annotations to be used on a single property.
DatabaseChangeProperty	Annotation used by AbstractChange to declare ChangeParameterMetaData information.
DbmsTargetedChange	Adding this interface to your Change class allows you to specify a dbms attribute listing the databases the change is applied to.
NormalizingStreamV8	Deprecated.
ReplaceIfExists	ReplaceIfExists interface will control whether an implementation change object class will set the replaceIfExists flag that basically will tell generate-changelog/diffToChangelog commands the given change object needs to generate the SQL for replace the stored logic if it already exists