dropPrimaryKey
The dropPrimaryKey
Change Type drops an existing primary key in the table.
Uses
You can typically use the dropPrimaryKey
Change Type when you want to remove a field that uniquely defines a record in your database. It can include tableName
and other attributes listed in this documentation.
Running the dropPrimaryKey
Change Type
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
Now, you should see that the information indicating your primary key is removed from the table.
Available attributes
Name | Description | Required for | Supports | Since |
| Name of the catalog | all | ||
| Name of the constraint (primary key) to drop | firebird, informix, sybase | all except bigquery | |
| Boolean: whether to drop the index associated with the primary key. | all | ||
| Name of the schema | all | ||
| Name of the table from which you drop the primary key. | all | all |
Database support
Database | Notes | |
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 |
dropPrimaryKey examples
--liquibase formatted sql
--changeset liquibase-docs:dropPrimaryKey-example
ALTER TABLE department.person
DROP PRIMARY KEY;