SQL/MX 3.2.1 Management Manual (H06.26+, J06.15+)

4. Enter the DROP TRIGGER statement.
5. Revise the application source code as needed to reflect your changes to the database. Process
and compile the updated source file. For more information, see the SQL/MX Programming
Manual for C and COBOL.
For more information, see the SQL/MX Reference Manual.
Dropping Views
To drop a view of SQL/MX data, use the DROP VIEW statement. To drop a view, you must be the
view owner, or own its schema or be the super ID.
The RESTRICT option, by default, will not allow a view to be dropped if it is referenced in the query
expression of any other view or in the search condition of another object's constraint. The CASCADE
option, if specified, will drop both the view and any such dependent objects
Dropping a view with dependencies is essentially the same as dropping the view and each of its
dependent objects separately. Although SQL can drop all dependent objects automatically, it does
not drop any dependent programs. Dropping a view invalidates all programs that use the view,
however, and HP recommends that you update and recompile these programs explicitly after
dropping the view to avoid errors and expensive, automatic recompilations.
For more information, see the SQL/MX Reference Manual.
Steps for Dropping a View
1. Start an MXCI session. Enter a LOG command to initiate a log file for statements and commands
entered in this session. Keep the log for your records.
2. Determine the name of the view you want to drop.
3. Enter the DROP VIEW statement.
4. Revise the application source code as needed to reflect your changes to the database. Process
and compile the updated source file. For more information, see the SQL/MX Programming
Manual for C and COBOL.
For more information, see the SQL/MX Reference Manual.
Dropping Objects From an SQL/MX Database 177