dropNotNullConstraint
Makes a column nullable.
Run dropNotNullConstraint
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 |
| Name of the catalog | all | 3.0 | |
| Data type of the column. To help make scripts database-independent, Liquibase automatically converts the following generic data types to the correct database implementation: Also, specifying a
For Snowflake, Liquibase also implements For Databricks, Liquibase also implements Note: To specify a complex Databricks type like For more information, see Liquibase Data Type Handling. | informix, mariadb, mssql, mysql | all | |
| Name of the column to drop the constraint from | all | all | |
| Name of the constraint to drop (if database supports names for
constraints) | -- | -- | -- |
| Name of the schema | all | ||
| Name of the table containing the column to drop the constraint from | all | all |
Database support
Database | Notes | |
DB2/LUW | Supported | Yes |
DB2/z | Not Supported | No |
Derby | Supported | Yes |
Firebird | Not Supported | No |
Google BigQuery | Supported | Yes |
H2 | Supported | Yes |
HyperSQL | Supported | Yes |
INGRES | Supported | Yes |
Informix | Supported | Yes |
MariaDB | Supported | Yes |
MySQL | Supported | Yes |
Oracle | Supported | Yes |
PostgreSQL | Supported | Yes |
Snowflake | Supported | Yes |
SQL Server | Supported | Yes |
SQLite | Not Supported | No |
Sybase | Supported | Yes |
Sybase Anywhere | Supported | Yes |
dropNotNullConstraint examples
--liquibase formatted sql
--changeset liquibase-docs:dropNotNullConstraint-example
ALTER TABLE cat.person MODIFY id INT NULL;