Additional DROP Processes for Java External Procedures
- The same validation of privileges that are required to drop a non-Java external procedure are performed for Java procedures.
- The database deletes the row in the DBC.Routine_Jar_Usage table that indicated that the Java routine being dropped used the JAR specified in its EXTERNAL NAME clause.
The request drops only the Java procedure, and any associations made to it from within the SQLJ database and dictionary tables. The request does not change the Java method or the JAR file associated with the Java external procedure.
DROP MACRO Referenced Objects
Dropping a table or view does not delete the views, macros, or stored procedures that reference the dropped table or view. You need to drop referencing views, macros, and stored procedures explicitly.
Views, macros, and stored procedures fail after you drop a referenced table or view. If you replace a dropped table or view, the referencing views, macros, and stored procedures operate and provide the expected results only if the replacements have the same structure.
You cannot drop a table on which a trigger or join index is defined. You must first drop the index or trigger, then drop the table definition.