1.1.1

Table Of Contents
-- SQL statement
-- using a quoted identifier for the
-- SQLFire jar name
CALL SQLJ.INSTALL_JAR('tours.jar', 'APP."Sample2"', 0)
SQLJ.REMOVE_JAR
The SQLJ.REMOVE_JAR system procedure removes an installed JAR le from SQLFire.
Syntax
SQLJ.REMOVE_JAR(IN QUALIFIED_JAR_NAME VARCHAR(32672),
IN UNDEPLOY INTEGER)
The SQLFire name of the JAR le, qualied by the schema name. (This should
correspond to the name that you specied in the SQLJ.INSTALL_JAR command.)
Two examples:
MYSCHEMA.Sample1
-- a delimited identifier.
MYSCHEMA."Sample2"
QUALIFIED_JAR_NAME
This integer argument is used to specify an alias for the JAR le. However,
SQLFire ignores this argument, so it is normally set to 0.
UNDEPLOY
Example
-- SQL statement
CALL SQLJ.REMOVE_JAR('APP.Sample1', 0)
SQLFire unloads the JAR le classes that were installed using the name "APP.Sample1."
SQLJ.REPLACE_JAR
The SQLJ.REPLACE_JAR system procedure replaces an installed JAR le in SQLFire.
Syntax
SQLJ.REPLACE_JAR(IN JAR_FILE_PATH VARCHAR(32672),
IN QUALIFIED_JAR_NAME VARCHAR(32672))
The path and physical name of the JAR le to use as a replacement. For example:
d:/todays_build/tours.jar
JAR_FILE_PATH
Note: The JAR le path must be available on the specic SQLFire data
store to which the client is connected. If the client connects directly to a
known SQLFire server, then only that server requires the JAR le to be
available at the specied path when the procedure executes. However, if
a client connects using a locator then they may be connected to any available
server in the distributed system. In this case, the JAR le path should be
available to all members of the SQLFire cluster (for example, from a
leshare location such as z:\) to ensure that the procedure can execute.
611
SQL Language Reference