Liquibase Enterprise was formerly known as Datical DB.
Oracle Edition-Based Redefinition
Datical supports Editioning Views. No special handling or configuration is required.
Note
The Oracle user (schema) must have ENABLE EDITIONS assigned. See Oracle documentation.
Editioning Views in Oracle
An editioning view is very much like any other view, except that it allows for the definition of more types of triggers on the view. It allows this because Editioning Views take the place of tables in an environment where Edition Based Redefinition is being used. In these environments, the editioning view is "like an API to the base table."
create table payment_manager.TESTING_B ( PAYMENT_STATUS_ID NUMBER, NAME VARCHAR2(64), DESCRIPTION VARCHAR2(512), CREATION_DATE TIMESTAMP(6) WITH LOCAL TIME ZONE, MODIFY_DATE TIMESTAMP(6) WITH LOCAL TIME ZONE ); CREATE OR REPLACE EDITIONING VIEW payment_manager.TESTING AS SELECT PAYMENT_STATUS_ID, NAME, DESCRIPTION, CREATION_DATE, MODIFY_DATE FROM payment_manager.TESTING_B;
Enabling Editions
Editions must be enabled on the user (schema owner).
ALTER USER <user> ENABLE EDITIONS;
Permissions for Editions
A user must have permissions to create and drop editions. Add these permissions to the Datical role.
GRANT CREATE ANY EDITION TO <role_or_user>; GRANT DROP ANY EDITION TO <role_or_user>;
Datical Support for Editioning Views
Datical supports the following operations for editioning views:
- Package SQL scripts (including snapshot and diff)
- Diffchangelog (generate editioning-view changesets from the result)
- Deploy
- Drop
Copyright © Liquibase 2012-2022 - Proprietary and Confidential