Reference
Version · 5.1
Reference guide

createView

Last updated: October 8, 2026

Creates a new database view.

Liquibase supports views, but does not support materialized views.

Known issue: The Liquibase createView 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 that you are using the Snowflake createView change type and breaks backwards compatibility with the Liquibase createView change type. We recommend upgrading to Liquibase Secure 5.1.1 to use createView with YAML and JSON change type formats successfully.

Uses

You can use the createView Change Type to create a view on a table. A view is a virtual table that stores the result of a particular SELECT SQL statement for easy access (without altering the table). For example, joining multiple tables into a single, easy-to-query object.

Note: The Liquibase extension for Databricks extends this Change Type to support Databricks features, including STRUCT and MAP variable types.

Run createView

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
`catalogName`	Name of the catalog		all
`encoding`	Encoding used in the file specified in the `path` attribute. Default: `UTF-8`. Note: Modifying the`{encoding\|fileEncoding}` setting causes checksum mismatches for previously applied changesets. If your changeset edits are safe and intentional, you can explicitly tell Liquibase to accept the new checksum using validCheckSum. See How to resolve checksum errors for more information.		all
`fullDefinition`	Set to `true` if `selectQuery` is the entire view definition. Set to `false` if the `CREATE VIEW` header should be added.		all
`path`	Path to file containing view definition. Using the `path` attribute is an alternative to `selectQuery`.		all
`relativeToChangelogFile`	Specifies whether the file path is relative to the changelog file rather than looked up in the search path. Default: `false`.		all
`remarks`	A short descriptive comment		all
`replaceIfExists`	If `true`, Liquibase uses `CREATE OR REPLACE` syntax when creating the view. Default: `false`. Available in Liquibase 1.5+.		databricks, db2, firebird, h2, hsqldb, ingres, mariadb, mssql, mysql, oracle, postgresql, sqlite, sybase
`schemaName`	Name of the schema		all
`selectQuery`	SQL for generating the view	informix	all
`tblProperties`	The table properties you want to specify. Specify properties using the format `'key'='value'`. Separate multiple properties using commas. Note: This attribute is only available with the Liquibase extension for Databricks. It is not available for SQL changelogs. For more information, see Databricks SQL Reference: CREATE VIEW.		databricks
`viewName`	Name of the view	all	all

Database support

Database	Notes	Auto Rollback
DB2/LUW	Supported	Yes
DB2/z	Supported	Yes
Derby	Supported	Yes
Firebird	Supported	Yes
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	Supported	Yes
Sybase	Supported	Yes
Sybase Anywhere	Supported	Yes

<?xml version="1.0" encoding="UTF-8"?>
<databaseChangeLog
        xmlns="http://www.liquibase.org/xml/ns/dbchangelog"
        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xsi:schemaLocation="http://www.liquibase.org/xml/ns/dbchangelog
        http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-latest.xsd">

    <changeSet id="create-basic-view" author="examples">
        <createView viewName="ACTIVE_CUSTOMERS">
            SELECT * FROM CUSTOMERS WHERE STATUS = 'ACTIVE'
        </createView>
        <rollback>
            <dropView viewName="ACTIVE_CUSTOMERS"/>
        </rollback>
    </changeSet>

    <changeSet id="create-replace-view" author="examples">
        <createView viewName="SALES_SUMMARY" replaceIfExists="true">
            SELECT REGION, SUM(AMOUNT) AS TOTAL FROM SALES GROUP BY REGION
        </createView>
        <rollback>
            <dropView viewName="SALES_SUMMARY"/>
        </rollback>
    </changeSet>

    <changeSet id="create-schema-view" author="examples">
        <createView viewName="REGIONAL_DATA" schemaName="ANALYTICS">
            SELECT SALES_REGION, SALES_COUNTRY, REVENUE FROM SALES_DATA
        </createView>
        <rollback>
            <dropView viewName="REGIONAL_DATA" schemaName="ANALYTICS"/>
        </rollback>
    </changeSet>

    <changeSet id="create-view-if-not-exists" author="examples">
        <preConditions onFail="MARK_RAN">
            <not>
                <viewExists viewName="QUARTERLY_REPORT"/>
            </not>
        </preConditions>
        <createView viewName="QUARTERLY_REPORT">
            SELECT QUARTER, SUM(SALES) FROM TRANSACTIONS GROUP BY QUARTER
        </createView>
        <rollback>
            <dropView viewName="QUARTERLY_REPORT"/>
        </rollback>
    </changeSet>

</databaseChangeLog>

{
  "databaseChangeLog": [
    {
      "changeSet": {
        "id": "create-basic-view",
        "author": "examples",
        "changes": [
          {
            "createView": {
              "viewName": "ACTIVE_CUSTOMERS",
              "selectQuery": "SELECT * FROM CUSTOMERS WHERE STATUS = 'ACTIVE'"
            }
          }
        ]
      }
    },
    {
      "changeSet": {
        "id": "create-secure-view",
        "author": "examples",
        "changes": [
          {
            "createView": {
              "viewName": "SALES_SUMMARY",
              "replaceIfExists": true,
              "secure": true,
              "comment": "Aggregated sales data by region",
              "selectQuery": "SELECT REGION, SUM(AMOUNT) AS TOTAL FROM SALES GROUP BY REGION"
            }
          }
        ]
      }
    },
    {
      "changeSet": {
        "id": "create-view-with-rap",
        "author": "examples",
        "changes": [
          {
            "createView": {
              "viewName": "REGIONAL_DATA",
              "schemaName": "ANALYTICS",
              "comment": "Region-restricted data view",
              "selectQuery": "SELECT SALES_REGION, SALES_COUNTRY, REVENUE FROM SALES_DATA",
              "rowAccessPolicy": {
                "policyName": "REGION_POLICY",
                "rowAccessPolicyColumns": [
                  {"column": {"columnName": "SALES_REGION"}},
                  {"column": {"columnName": "SALES_COUNTRY"}}
                ]
              }
            }
          }
        ]
      }
    }
  ]
}

databaseChangeLog:
  # Basic view
  - changeSet:
      id: create-basic-view
      author: examples
      changes:
        - createView:
            viewName: ACTIVE_CUSTOMERS
            selectQuery: SELECT * FROM CUSTOMERS WHERE STATUS = 'ACTIVE'

  # Secure view with OR REPLACE and comment
  - changeSet:
      id: create-secure-view
      author: examples
      changes:
        - createView:
            viewName: SALES_SUMMARY
            replaceIfExists: true
            secure: true
            comment: Aggregated sales data by region
            selectQuery: SELECT REGION, SUM(AMOUNT) AS TOTAL FROM SALES GROUP BY REGION

  # View with row access policy
  - changeSet:
      id: create-view-with-rap
      author: examples
      changes:
        - createView:
            viewName: REGIONAL_DATA
            schemaName: ANALYTICS
            comment: Region-restricted data view
            selectQuery: SELECT SALES_REGION, SALES_COUNTRY, REVENUE FROM SALES_DATA
            rowAccessPolicy:
              policyName: REGION_POLICY
              rowAccessPolicyColumns:
                - column:
                    columnName: SALES_REGION
                - column:
                    columnName: SALES_COUNTRY

-- Basic view
CREATE VIEW MYDB.PUBLIC.ACTIVE_CUSTOMERS
AS SELECT * FROM CUSTOMERS WHERE STATUS = 'ACTIVE';

-- Secure view with OR REPLACE and comment
CREATE OR REPLACE SECURE VIEW MYDB.PUBLIC.SALES_SUMMARY
  COMMENT = 'Aggregated sales data by region'
AS SELECT REGION, SUM(AMOUNT) AS TOTAL FROM SALES GROUP BY REGION;

-- View with row access policy
CREATE VIEW MYDB.ANALYTICS.REGIONAL_DATA
  COMMENT = 'Region-restricted data view'
  WITH ROW ACCESS POLICY REGION_POLICY ON (SALES_REGION, SALES_COUNTRY)
AS SELECT SALES_REGION, SALES_COUNTRY, REVENUE FROM SALES_DATA;

-- View with IF NOT EXISTS
CREATE VIEW IF NOT EXISTS MYDB.PUBLIC.QUARTERLY_REPORT
AS SELECT QUARTER, SUM(SALES) FROM TRANSACTIONS GROUP BY QUARTER;

<?xml version="1.0" encoding="UTF-8"?>
<databaseChangeLog
        xmlns="http://www.liquibase.org/xml/ns/dbchangelog"
        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xsi:schemaLocation="http://www.liquibase.org/xml/ns/dbchangelog
        http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-latest.xsd">

    <changeSet id="create-basic-view" author="examples">
        <createView viewName="ACTIVE_CUSTOMERS">
            SELECT * FROM CUSTOMERS WHERE STATUS = 'ACTIVE'
        </createView>
        <rollback>
            <dropView viewName="ACTIVE_CUSTOMERS"/>
        </rollback>
    </changeSet>

    <changeSet id="create-replace-view" author="examples">
        <createView viewName="SALES_SUMMARY" replaceIfExists="true">
            SELECT REGION, SUM(AMOUNT) AS TOTAL FROM SALES GROUP BY REGION
        </createView>
        <rollback>
            <dropView viewName="SALES_SUMMARY"/>
        </rollback>
    </changeSet>

    <changeSet id="create-schema-view" author="examples">
        <createView viewName="REGIONAL_DATA" schemaName="ANALYTICS">
            SELECT SALES_REGION, SALES_COUNTRY, REVENUE FROM SALES_DATA
        </createView>
        <rollback>
            <dropView viewName="REGIONAL_DATA" schemaName="ANALYTICS"/>
        </rollback>
    </changeSet>

    <changeSet id="create-view-if-not-exists" author="examples">
        <preConditions onFail="MARK_RAN">
            <not>
                <viewExists viewName="QUARTERLY_REPORT"/>
            </not>
        </preConditions>
        <createView viewName="QUARTERLY_REPORT">
            SELECT QUARTER, SUM(SALES) FROM TRANSACTIONS GROUP BY QUARTER
        </createView>
        <rollback>
            <dropView viewName="QUARTERLY_REPORT"/>
        </rollback>
    </changeSet>

</databaseChangeLog>

{
  "databaseChangeLog": [
    {
      "changeSet": {
        "id": "create-basic-view",
        "author": "examples",
        "changes": [
          {
            "createView": {
              "viewName": "ACTIVE_CUSTOMERS",
              "selectQuery": "SELECT * FROM CUSTOMERS WHERE STATUS = 'ACTIVE'"
            }
          }
        ]
      }
    },
    {
      "changeSet": {
        "id": "create-secure-view",
        "author": "examples",
        "changes": [
          {
            "createView": {
              "viewName": "SALES_SUMMARY",
              "replaceIfExists": true,
              "secure": true,
              "comment": "Aggregated sales data by region",
              "selectQuery": "SELECT REGION, SUM(AMOUNT) AS TOTAL FROM SALES GROUP BY REGION"
            }
          }
        ]
      }
    },
    {
      "changeSet": {
        "id": "create-view-with-rap",
        "author": "examples",
        "changes": [
          {
            "createView": {
              "viewName": "REGIONAL_DATA",
              "schemaName": "ANALYTICS",
              "comment": "Region-restricted data view",
              "selectQuery": "SELECT SALES_REGION, SALES_COUNTRY, REVENUE FROM SALES_DATA",
              "rowAccessPolicy": {
                "policyName": "REGION_POLICY",
                "rowAccessPolicyColumns": [
                  {"column": {"columnName": "SALES_REGION"}},
                  {"column": {"columnName": "SALES_COUNTRY"}}
                ]
              }
            }
          }
        ]
      }
    }
  ]
}

databaseChangeLog:
  # Basic view
  - changeSet:
      id: create-basic-view
      author: examples
      changes:
        - createView:
            viewName: ACTIVE_CUSTOMERS
            selectQuery: SELECT * FROM CUSTOMERS WHERE STATUS = 'ACTIVE'

  # Secure view with OR REPLACE and comment
  - changeSet:
      id: create-secure-view
      author: examples
      changes:
        - createView:
            viewName: SALES_SUMMARY
            replaceIfExists: true
            secure: true
            comment: Aggregated sales data by region
            selectQuery: SELECT REGION, SUM(AMOUNT) AS TOTAL FROM SALES GROUP BY REGION

  # View with row access policy
  - changeSet:
      id: create-view-with-rap
      author: examples
      changes:
        - createView:
            viewName: REGIONAL_DATA
            schemaName: ANALYTICS
            comment: Region-restricted data view
            selectQuery: SELECT SALES_REGION, SALES_COUNTRY, REVENUE FROM SALES_DATA
            rowAccessPolicy:
              policyName: REGION_POLICY
              rowAccessPolicyColumns:
                - column:
                    columnName: SALES_REGION
                - column:
                    columnName: SALES_COUNTRY

-- Basic view
CREATE VIEW MYDB.PUBLIC.ACTIVE_CUSTOMERS
AS SELECT * FROM CUSTOMERS WHERE STATUS = 'ACTIVE';

-- Secure view with OR REPLACE and comment
CREATE OR REPLACE SECURE VIEW MYDB.PUBLIC.SALES_SUMMARY
  COMMENT = 'Aggregated sales data by region'
AS SELECT REGION, SUM(AMOUNT) AS TOTAL FROM SALES GROUP BY REGION;

-- View with row access policy
CREATE VIEW MYDB.ANALYTICS.REGIONAL_DATA
  COMMENT = 'Region-restricted data view'
  WITH ROW ACCESS POLICY REGION_POLICY ON (SALES_REGION, SALES_COUNTRY)
AS SELECT SALES_REGION, SALES_COUNTRY, REVENUE FROM SALES_DATA;

-- View with IF NOT EXISTS
CREATE VIEW IF NOT EXISTS MYDB.PUBLIC.QUARTERLY_REPORT
AS SELECT QUARTER, SUM(SALES) FROM TRANSACTIONS GROUP BY QUARTER;

PreviouscreateTrigger NextdisableTrigger

createView

Uses

Run createView

Available attributes

Database support

XML example

JSON example

YAML example

SQL example