Importing a Stored Procedure¶

The statement CREATE PROCEDURE adds a new stored procedure to the Virtual DataPort Server.

CREATE [OR REPLACE] PROCEDURE <name:identifier>
    CLASSNAME <className:literal>
    [ CLASSPATH <classPath:literal> ]
    [ JARS <jar name:literal> [, <jar name:literal>]* ]
    [ FOLDER = <literal> ]
    [ DESCRIPTION = <literal> ]
    [ CHECK_INDIRECT_ACCESS { ON | OFF} ]

CLASSNAME: name of the Java class that implements the stored procedure. This class must be loaded into the Server (see the section Importing Extensions of the Administration Guide).

CLASSPATH: list of paths to the jar files that contains the Java classes of the procedure. Although you can use this parameter, we recommend importing the jar files into the Virtual DataPort server and then, reference them from the JARS clause. That way, you do not depend on these jars being on a particular location.

JARS: list of names of the jar files that have been uploaded to the Virtual DataPort server and that this procedure depends on.

CHECK_INDIRECT_ACCESS: if this option is defined with ON value, the INDIRECT_ACCESS privilege will be checked for the view (Only when the privilege is enabled at server level).

The use of the OR REPLACE modifier specifies that, if there is a procedure with the name indicated, this must be replaced by the new procedure. This will lead to the recalculation of the schemas and query capabilities of the derived views using the procedure.

Once created, a stored procedure can be modified using the ALTER PROCEDURE statement.

ALTER PROCEDURE <name:identifier>
    [ CLASSNAME <className:literal> ]
    [ CLASSPATH = <classPath:literal> [<classPath:literal> ]* ]
    [ JARS <jar name:literal> [, <jar name:literal>]* ]
    [ CHECK_INDIRECT_ACCESS { ON | OFF} ]

The meaning of the CLASSNAME and CLASSPATH clauses is the same for the CREATE PROCEDURE statement.