Example 1: Deleting a view definition

    The following example deletes the view definition CURRENT_INFO:

    SQL> DROP VIEW CURRENT_INFO;
    SQL> COMMIT;

    Example 2: Deleting a view with dependent views

    This example shows that SQL will not automatically delete any
    views that refer to the view named in the DROP VIEW statement.
    You must use the CASCADE keyword to delete a view with dependent
    views.

    SQL> DROP VIEW CURRENT_JOB;
    %RDB-E-NO_META_UPDATE, metadata update failed
    -RDMS-F-VIEWINVIEW, view CURRENT_JOB is referenced by view CURRENT_INFO
    -RDMS-F-VIEWNOTDEL, view CURRENT_JOB has not been deleted

    SQL> DROP VIEW CURRENT_JOB CASCADE;
    View CURRENT_INFO is also being dropped.
    SQL> COMMIT;

    Example 3: Adding new definitions to a database

    When updating metadata definitions using a predefined SQL script
    it sometimes required to remove objects that may not be present
    in all databases being maintained. Adding a DROP VIEW, for
    instance, will result in an error as shown here.

    SQL> drop view CURRENT_INFO;
    %SQL-F-RELNOTDEF, Table CURRENT_INFO is not defined in database or schema
    SQL> create view CURRENT_INFO
    cont> ...etc...

    By using the IF EXISTS clause the error message is supressed and
    makes for a less confusing execution of the maintance script.

    SQL> drop view CURRENT_INFO if exists;
    SQL> create view CURRENT_INFO
    cont> ...etc...