liquibase.change.core
Class RenameViewChange
java.lang.Object
liquibase.change.AbstractChange
liquibase.change.core.RenameViewChange
- All Implemented Interfaces:
- Change, LiquibaseSerializable
public class RenameViewChange
- extends AbstractChange
Renames an existing view.
Methods inherited from class liquibase.change.AbstractChange |
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, supports, supportsRollback, toString, validate, warn |
RenameViewChange
public RenameViewChange()
getCatalogName
public String getCatalogName()
setCatalogName
public void setCatalogName(String catalogName)
getSchemaName
public String getSchemaName()
setSchemaName
public void setSchemaName(String schemaName)
getOldViewName
public String getOldViewName()
setOldViewName
public void setOldViewName(String oldViewName)
getNewViewName
public String getNewViewName()
setNewViewName
public void setNewViewName(String newViewName)
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)
.
createInverses
protected Change[] createInverses()
- Description copied from class:
AbstractChange
- Create inverse changes that can roll back this change. This method is intended
to be overriden by Change implementations that have a logical inverse operation. Default implementation returns null.
If
AbstractChange.generateRollbackStatements(liquibase.database.Database)
is overridden, this method may not be called.
- Overrides:
createInverses
in class AbstractChange
- Returns:
- Return null if there is no corresponding inverse and therefore automatic rollback is not possible. Return an empty array to have a no-op rollback.
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 © 2016 Liquibase.org. All rights reserved.