SQLJ.REMOVE_JAR system procedure
Derby Reference Manual
180
MYSCHEMA.Sample1
-- a delimited identifier
MYSCHEMA."Sample2"
DEPLOY
If set to 1, indicates the existence of an SQLJ deployment descriptor file. Derby
ignores this argument, so it is normally set to 0.
Execute privileges
If authentication and SQL authorization are both enabled, only the
execute privileges on this procedure by default. See "Enabling user authentication" and
"Setting the SQL standard authorization mode" in the Derby Developer's Guide for more
information. The database owner can grant access to other users.
SQL examples
-- SQL statement
-- install jar from current directory
CALL SQLJ.INSTALL_JAR('tours.jar', 'APP.Sample1', 0)
-- SQL statement
-- install jar using full path
CALL SQLJ.INSTALL_JAR('c:\myjarfiles\tours.jar', 'APP.Sample1', 0)
-- SQL statement
-- install jar from remote location
CALL SQLJ.INSTALL_JAR('http://www.example.com/tours.jar', 'APP.Sample2',
0)
-- SQL statement
-- install jar using a quoted identifier for the
-- Derby jar name
CALL SQLJ.INSTALL_JAR('tours.jar', 'APP."Sample3"', 0)
SQLJ.REMOVE_JAR system procedure
The SQLJ.REMOVE_JAR system procedure removes a jar file from a database.
Syntax
SQLJ.REMOVE_JAR(IN QUALIFIED_JAR_NAME VARCHAR(32672),
IN UNDEPLOY INTEGER)
QUALIFIED_JAR_NAME
The Derby name of the jar file, qualified by the schema name. Two examples:
MYSCHEMA.Sample1
-- a delimited identifier.
MYSCHEMA."Sample2"
UNDEPLOY
If set to 1, indicates the existence of an SQLJ deployment descriptor file. Derby
ignores this argument, so it is normally set to 0.
Execute privileges
If authentication and SQL authorization are both enabled, only the
execute privileges on this procedure by default. See "Enabling user authentication" and
"Setting the SQL standard authorization mode" in the Derby Developer's Guide for more
information. The database owner can grant access to other users.
SQL example
-- SQL statement
