public class AddLookupTableChange extends AbstractChange
LiquibaseSerializable.SerializationType
NODENAME_COLUMN
EMPTY_CHANGE
GENERIC_CHANGELOG_EXTENSION_NAMESPACE, GENERIC_SNAPSHOT_EXTENSION_NAMESPACE, STANDARD_CHANGELOG_NAMESPACE, STANDARD_SNAPSHOT_NAMESPACE
PRIORITY_DEFAULT, PRIORITY_NOT_APPLICABLE, PRIORITY_SPECIALIZED
Constructor and Description |
---|
AddLookupTableChange() |
createChangeMetaData, createChangeParameterMetadata, createDescriptionMetaData, createEmptyColumnConfig, createExampleValueMetaData, createMustEqualExistingMetaData, createRequiredDatabasesMetaData, createSerializationTypeMetaData, createSinceMetaData, createSupportedDatabasesMetaData, customLoadLogic, finishInitialization, generateCheckSum, generateRollbackStatements, generateRollbackStatementsVolatile, generateStatementsVolatile, getAffectedDatabaseObjects, getChangeSet, getDescription, getResourceAccessor, getSerializableFieldNamespace, getSerializableFields, getSerializableFieldType, getSerializableFieldValue, getSerializedObjectName, isInvalidProperty, load, serialize, serializeValue, setChangeSet, setResourceAccessor, supportsRollback, toString, warn
clone, describe, equals, get, get, get, getAttributes, getFieldValue, getObjectMetaData, getValuePath, has, hashCode, set
finalize, getClass, notify, notifyAll, wait, wait, wait
clone, describe, get, get, getAttributes, getObjectMetaData, getValuePath, has, set
public ValidationErrors validate(Database database)
AbstractChange
SqlGenerator.validate(liquibase.statement.SqlStatement,
liquibase.database.Database, liquibase.sqlgenerator.SqlGeneratorChain)
method on the SqlStatement
objects returned by Change.generateStatements(liquibase.database.Database)
.
If no or null SqlStatements are returned by generateStatements then this method returns no errors.
If there are no parameters than this method returns no errorsvalidate
in interface Change
validate
in class AbstractChange
public String getExistingTableCatalogName()
public void setExistingTableCatalogName(String existingTableCatalogName)
public String getExistingTableSchemaName()
public void setExistingTableSchemaName(String existingTableSchemaName)
public String getExistingTableName()
public void setExistingTableName(String existingTableName)
public String getExistingColumnName()
public void setExistingColumnName(String existingColumnName)
public String getNewTableCatalogName()
public void setNewTableCatalogName(String newTableCatalogName)
public String getNewTableSchemaName()
public void setNewTableSchemaName(String newTableSchemaName)
public String getNewTableName()
public void setNewTableName(String newTableName)
public String getNewColumnName()
public void setNewColumnName(String newColumnName)
public String getNewColumnDataType()
public void setNewColumnDataType(String newColumnDataType)
public String getConstraintName()
public String getFinalConstraintName()
public void setConstraintName(String constraintName)
public boolean supports(Database database)
AbstractChange
SqlGenerator.supports(liquibase.statement.SqlStatement, liquibase.database.Database)
method on the SqlStatement
objects returned by Change.generateStatements(liquibase.database.Database)
.
If no or null SqlStatements are returned by generateStatements then this method returns true.
If AbstractChange.generateStatementsVolatile(liquibase.database.Database)
returns true, we cannot call generateStatements and so assume true.supports
in interface Change
supports
in class AbstractChange
protected Change[] createInverses()
AbstractChange
AbstractChange.generateRollbackStatements(liquibase.database.Database)
is overridden, this method may not be called.createInverses
in class AbstractChange
#supportsRollback
public SqlStatement[] generateStatements(Database database)
Change
SqlStatement
objects required to run the change for the given database.
NOTE: This method may be called multiple times throughout the changelog execution process and may be called in documentation generation and other integration points as well.
If this method reads from the current database state or uses any other logic that will be affected by whether previous changeSets have ran or not, you must return true from Change.generateStatementsVolatile(liquibase.database.Database)
.public ChangeStatus checkStatus(Database database)
Change
checkStatus
in interface Change
checkStatus
in class AbstractChange
public String getConfirmationMessage()
Change
public String getSerializedObjectNamespace()
getSerializedObjectNamespace
in interface LiquibaseSerializable
getSerializedObjectNamespace
in class AbstractChange
Copyright © 2023 Liquibase.org. All rights reserved.