REMOVE Statement

Removes a class, a package, or a JAR file from a database. Removed classes are no longer available for use as a variable type. Any class, package, or JAR to be removed must already be installed.

Quick Links:

Go to Parameters

Go to Examples

Go to Standards

Go to Permissions

Syntax

REMOVE JAVA classes_to_remove

classes_to_remove
   { CLASS java_class_name [, java_class_name ]… 
   | PACKAGE java_package_name [, java_package_name ]… 
   | JAR jar_name [, jar_name ]… [ RETAIN CLASSES ] }

Parameters

(back to top)

java_class_name – he name of one or more Java classes to be removed. Those classes must be installed classes in the current database.

java_package_name – he name of one or more Java packages to be removed. Those packages must be the name of packages in the current database.

jar_name – a character string value of maximum length 255. Each jar_name must be equal to the jar_name of a retained JAR in the current database. Equality of jar_name is determined by the character string comparison rules of the SQL system.

RETAIN CLASSES – the specified JARs are no longer retained in the database, and the retained classes have no associated JAR. If RETAIN CLASSES is specified, this is the only action of the REMOVE statement.

Examples

(back to top)

Example 1 – remove a Java class named “Demo” from the current database:
```
REMOVE JAVA CLASS Demo
```

Standards

(back to top)

SQL—Vendor extension to ISO/ANSI SQL grammar.
SAP Sybase Database product—Not supported by Adaptive Server. A similar feature is available in an Adaptive Server-compatible manner using nested transactions.

Permissions

(back to top)

Requires one of:

MANAGE ANY EXTERNAL OBJECT system privilege.
You own the object.