liquibase.change.core
Class DropForeignKeyConstraintChange
java.lang.Object
liquibase.change.AbstractChange
liquibase.change.core.DropForeignKeyConstraintChange
- All Implemented Interfaces:
- Change, LiquibaseSerializable
public class DropForeignKeyConstraintChange
- extends AbstractChange
Drops an existing foreign key constraint.
Methods inherited from class liquibase.change.AbstractChange |
createChangeMetaData, createChangeParameterMetadata, createDescriptionMetaData, createExampleValueMetaData, createInverses, createMustEqualExistingMetaData, createRequiredDatabasesMetaData, createSerializationTypeMetaData, createSinceMetaData, createSupportedDatabasesMetaData, customLoadLogic, finishInitialization, generateCheckSum, generateRollbackStatements, generateRollbackStatementsVolatile, generateStatementsVolatile, getAffectedDatabaseObjects, getChangeSet, getResourceAccessor, getSerializableFieldNamespace, getSerializableFields, getSerializableFieldType, getSerializableFieldValue, getSerializedObjectName, isInvalidProperty, load, serialize, serializeValue, setChangeSet, setResourceAccessor, supports, supportsRollback, toString, validate, warn |
DropForeignKeyConstraintChange
public DropForeignKeyConstraintChange()
getBaseTableCatalogName
public String getBaseTableCatalogName()
setBaseTableCatalogName
public void setBaseTableCatalogName(String baseTableCatalogName)
getBaseTableSchemaName
public String getBaseTableSchemaName()
setBaseTableSchemaName
public void setBaseTableSchemaName(String baseTableSchemaName)
getBaseTableName
public String getBaseTableName()
setBaseTableName
public void setBaseTableName(String baseTableName)
getConstraintName
public String getConstraintName()
setConstraintName
public void setConstraintName(String constraintName)
generateStatements
public SqlStatement[] generateStatements(Database database)
- Description copied from interface:
Change
- Generates the
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)
.
checkStatus
public ChangeStatus checkStatus(Database database)
- Description copied from interface:
Change
- Validate that this change executed successfully against the given database. This will check that the update completed at a high level plus check details of the change.
For example, a change to add a column will check that the column exists plus data type, default values, etc.
- Specified by:
checkStatus
in interface Change
- Overrides:
checkStatus
in class AbstractChange
getConfirmationMessage
public String getConfirmationMessage()
- Description copied from interface:
Change
- Confirmation message to be displayed after the change is executed. Should include relevant configuration settings to make it as helpful as possible.
This method may be called outside the changelog execution process, such as in documentation generation.
getSerializedObjectNamespace
public String getSerializedObjectNamespace()
- Specified by:
getSerializedObjectNamespace
in interface LiquibaseSerializable
- Overrides:
getSerializedObjectNamespace
in class AbstractChange
Copyright © 2015 Liquibase.org. All rights reserved.