public class AddNotNullConstraintChange extends AbstractChange
LiquibaseSerializable.SerializationTypeNODENAME_COLUMNGENERIC_CHANGELOG_EXTENSION_NAMESPACE, GENERIC_SNAPSHOT_EXTENSION_NAMESPACE, STANDARD_CHANGELOG_NAMESPACE, STANDARD_SNAPSHOT_NAMESPACE| Constructor and Description |
|---|
AddNotNullConstraintChange() |
| Modifier and Type | Method and Description |
|---|---|
protected Change[] |
createInverses()
Create inverse changes that can roll back this change.
|
SqlStatement[] |
generateStatements(Database database)
Generates the
SqlStatement objects required to run the change for the given database. |
String |
getCatalogName() |
String |
getColumnDataType() |
String |
getColumnName() |
String |
getConfirmationMessage()
Confirmation message to be displayed after the change is executed.
|
String |
getConstraintName() |
String |
getDefaultNullValue() |
String |
getSchemaName() |
String |
getSerializedObjectNamespace() |
String |
getTableName() |
Boolean |
getValidate()
In certain SQL dialects, the VALIDATE keyword defines whether a NOT NULL constraint on a column in a table
should be checked if it refers to a valid row or not.
|
void |
setCatalogName(String catalogName) |
void |
setColumnDataType(String columnDataType) |
void |
setColumnName(String columnName) |
void |
setConstraintName(String constraintName) |
void |
setDefaultNullValue(String defaultNullValue) |
void |
setSchemaName(String schemaName) |
void |
setTableName(String tableName) |
void |
setValidate(Boolean shouldValidate) |
checkStatus, 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, warnpublic String getCatalogName()
public void setCatalogName(String catalogName)
public String getSchemaName()
public void setSchemaName(String schemaName)
public String getTableName()
public void setTableName(String tableName)
public String getColumnName()
public void setColumnName(String columnName)
public String getDefaultNullValue()
public void setDefaultNullValue(String defaultNullValue)
public String getColumnDataType()
public void setColumnDataType(String columnDataType)
public String getConstraintName()
public void setConstraintName(String constraintName)
public SqlStatement[] generateStatements(Database database)
ChangeSqlStatement 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).protected Change[] createInverses()
AbstractChangeAbstractChange.generateRollbackStatements(liquibase.database.Database) is overridden, this method may not be called.createInverses in class AbstractChange#supportsRollbackpublic String getConfirmationMessage()
Changepublic String getSerializedObjectNamespace()
getSerializedObjectNamespace in interface LiquibaseSerializablegetSerializedObjectNamespace in class AbstractChangepublic Boolean getValidate()
public void setValidate(Boolean shouldValidate)
shouldValidate - - if shouldValidate is set to FALSE then the constraint will be created
with the 'ENABLE NOVALIDATE' mode. This means the constraint would be created, but that no
check will be done to ensure old data has valid not null constrain - only new data would be checked
to see if it complies with the constraint logic. The default state for not null constrain is to
have 'ENABLE VALIDATE' set.Copyright © 2019 Liquibase.org. All rights reserved.