Class AddPrimaryKeyStatement

java.lang.Object
liquibase.statement.AbstractSqlStatement
liquibase.statement.core.AddPrimaryKeyStatement
All Implemented Interfaces:
SqlStatement

public class AddPrimaryKeyStatement extends AbstractSqlStatement
  • Constructor Details

    • AddPrimaryKeyStatement

      public AddPrimaryKeyStatement(String catalogName, String schemaName, String tableName, String columnNames, String constraintName)
      Deprecated.
    • AddPrimaryKeyStatement

      public AddPrimaryKeyStatement(String catalogName, String schemaName, String tableName, ColumnConfig[] columns, String constraintName)
  • Method Details

    • setTablespace

      public AddPrimaryKeyStatement setTablespace(String tablespace)
    • getColumnNames

      public String getColumnNames()
    • isClustered

      public Boolean isClustered()
    • setClustered

      public AddPrimaryKeyStatement setClustered(Boolean clustered)
    • shouldValidate

      public boolean shouldValidate()
      The VALIDATE keyword defines whether a primary key constraint on a column in a table should be checked if it refers to a valid row or not.
      Returns:
      true if ENABLE VALIDATE (this is the default), or false if ENABLE NOVALIDATE.
    • setShouldValidate

      public AddPrimaryKeyStatement setShouldValidate(boolean shouldValidate)
      Parameters:
      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 primary keys - only new data would be checked to see if it complies with the constraint logic. The default state for primary keys is to have 'ENABLE VALIDATE' set.
    • getCatalogName

      public String getCatalogName()
    • getSchemaName

      public String getSchemaName()
    • getTableName

      public String getTableName()