dropView
Last updated: March 26, 2026
Last updated: March 25, 2026
Drops an existing view. Liquibase supports views, but does not support materialized views.
Known issue: The Liquibase dropView change type is not compatible for Snowflake users in Liquibase Secure 5.1 using YAML or JSON change type formats. This does not affect XML change types at all. If you’re connecting to a Snowflake database, Liquibase automatically detects you are using the Snowflake dropView change type and breaks backwards compatibility with the Liquibase dropView change type. We recommend upgrading to Liquibase Secure 5.1.1 to use createView with YAML and JSON change type formats successfully.
Run dropView
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
updatecommand:liquibase update
Available attributes
Name | Description | Required for | Supports | Since |
| Name of the catalog | all | 3.0 | |
| Appends | all except oracle, firebird | 4.19.0 | |
| Name of the schema | all | ||
| Name of the view |
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 | Supported | No |
Sybase | Supported | No |
Sybase Anywhere | Supported | No |