[DERBY-2202] DROP PROCEDURE depends on SET SCHEMA

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 10.2.2.0
• Fix Version/s: 10.2.2.1, 10.3.1.4
• Component/s: SQL
• Environment: Sun Solaris;; java version "1.4.1_06"; Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_06-b01); Java HotSpot(TM) Client VM (build 1.4.1_06-b01, mixed mode)
• Urgency: Normal
• Assignee: Yip Ng
• Reporter: Bernhard Bodenstorfer
• Created: 28/Dec/06 13:51
• Updated: 05/Jul/10 17:12
• Resolved: 01/Jan/07 21:13

Description

This is possibly related to Bug https://issues.apache.org/jira/browse/DERBY-1304.

Use ij to execute the following statements:

CREATE SCHEMA datamgmt;
CREATE PROCEDURE datamgmt.exit ( IN value INTEGER )
MODIFIES SQL DATA
PARAMETER STYLE JAVA
LANGUAGE JAVA
EXTERNAL NAME 'java.lang.System.exit'
;
DROP PROCEDURE datamgmt.exit;
DROP SCHEMA datamgmt RESTRICT;

Then execute exactly the same lines once again. Then statement "DROP PROCEDURE datamgmt.exit" yields:

ERROR 42X94: PROCEDURE 'EXIT' does not exist.

However, if the DROP works if a default schema (SET SCHEMA) is used instead of the prefixed schemaName. That is, the following lines can be executed more than once in a row:

CREATE SCHEMA datamgmt;
CREATE PROCEDURE datamgmt.exit ( IN value INTEGER )
MODIFIES SQL DATA
PARAMETER STYLE JAVA
LANGUAGE JAVA
EXTERNAL NAME 'java.lang.System.exit'
;
SET SCHEMA datamgmt;
DROP PROCEDURE exit;
DROP SCHEMA datamgmt RESTRICT;

Therefore, SET SCHEMA can be used as a workaround, hence minor importance.