Uses of Package
liquibase.change
Package
Description
Liquibase top level namespace package.
The change package contains the available database "changes".
Technically, a Change expresses an intention for alter the structure of the Database.
Although Liquibase tries to provide a wide range of database refactorings, there are times you may want to create
your own custom refactoring class.
-
ClassDescriptionCheckSums are used by liquibase to determine if a Change has been modified since it was originally ran.
-
ClassDescriptionStandard superclass to simplify
Change
implementations.Interface all changes (refactorings) implement.Factory class for constructing the correct liquibase.change.Change implementation based on a command name.Static metadata about alink Change
.Static metadata about aChange
parameter.CheckSums are used by liquibase to determine if a Change has been modified since it was originally ran.The standard configuration used by Change classes to represent a column.The standard configuration used by Change classes to represent a constraints on a column.Annotation used byAbstractChange
to declareChangeParameterMetaData
information.Adding this interface to your Change class allows you to specify a dbms attribute listing the databases the change is applied to. -
ClassDescriptionStandard superclass to simplify
Change
implementations.A common parent for all raw SQL related changes regardless of where the sql was sourced from.Interface all changes (refactorings) implement.Markers a Change class as containing one or moreColumnConfig
configuration.CheckSums are used by liquibase to determine if a Change has been modified since it was originally ran.The standard configuration used by Change classes to represent a column.Annotation used byAbstractChange
to declareChangeMetaData
information.Container object which allows multipleDatabaseChangeProperty
annotations to be used on a single property.Annotation used byAbstractChange
to declareChangeParameterMetaData
information.Adding this interface to your Change class allows you to specify a dbms attribute listing the databases the change is applied to.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 -
ClassDescriptionStandard superclass to simplify
Change
implementations.Interface all changes (refactorings) implement.CheckSums are used by liquibase to determine if a Change has been modified since it was originally ran.Annotation used byAbstractChange
to declareChangeMetaData
information.Annotation used byAbstractChange
to declareChangeParameterMetaData
information. -
-
-
ClassDescriptionCheckSums are used by liquibase to determine if a Change has been modified since it was originally ran.
-
-
ClassDescriptionInterface all changes (refactorings) implement.The standard configuration used by Change classes to represent a column.
-
-
-
ClassDescriptionInterface all changes (refactorings) implement.The standard configuration used by Change classes to represent a column.
-
-
-
-
ClassDescriptionA common parent for all raw SQL related changes regardless of where the sql was sourced from.
-
ClassDescriptionA common parent for all raw SQL related changes regardless of where the sql was sourced from.
-
ClassDescriptionThe standard configuration used by Change classes to represent a column.
-
ClassDescriptionCheckSums are used by liquibase to determine if a Change has been modified since it was originally ran.
-
-
ClassDescriptionThe standard configuration used by Change classes to represent a column.
-
ClassDescriptionThe standard configuration used by Change classes to represent a column.Annotation used by
AbstractChange
to declareChangeParameterMetaData
information. -
ClassDescriptionThe standard configuration used by Change classes to represent a column.