dropUniqueConstraint
Drops an existing unique constraint.
Note: For OracleDB, the index associated with the constraint is also dropped.
Run dropUniqueConstraint
To run this Change Type, follow these steps:
- Add the Change Type to your changeset, as shown in the examples on this page.
- Specify any required attributes. Use the table on this page to see which ones your database requires.
- Deploy your changeset by running the
update
command:
liquibase update
Available attributes
Name | Description | Required for | Supports | Since |
---|---|---|---|---|
catalogName
|
Name of the catalog |
all | 3.0 | |
constraintName
|
Name of the constraint |
all | all | |
schemaName
|
Name of the schema |
all | ||
tableName
|
Name of the table to drop the unique constraint from | all | all | |
uniqueColumns
|
For SAP SQL Anywhere, a list of columns in the UNIQUE clause |
sybase |
Examples
SQL example
--liquibase formatted sql
--changeset liquibase-docs:dropUniqueConstraint-example
ALTER TABLE cat.person DROP KEY const_name;
Database support
Database | Notes | Auto Rollback |
---|---|---|
DB2/LUW | Supported | No |
DB2/z | Supported | No |
Derby | Supported | No |
Firebird | Supported | No |
Google BigQuery | Supported | No |
H2 | Supported | No |
HyperSQL | Supported | No |
INGRES | Supported | No |
Informix | Supported | No |
MariaDB | Supported | No |
MySQL | Supported | No |
Oracle | Supported | No |
PostgreSQL | Supported | No |
Snowflake | Supported | No |
SQL Server | Supported | No |
SQLite | Not Supported | No |
Sybase | Supported | No |
Sybase Anywhere | Supported | No |