A module is simply a collection of routines. All the routines in a module are created by declaring them when the module is created. Routines cannot be added to or removed from a module after the module has been created.
A module belongs to the schema in which it is created and all the routines contained in a module must belong to the same schema as the module.
The name of a routine in a module may be qualified in the normal way by using the name of the schema to which the routine belongs. The module name is never used to qualify the name of a routine.
Note: It is not possible to grant EXECUTE privilege on a module. In order to allow an ident to invoke a routine, whether it exists on its own or in a module, EXECUTE privilege on the routine must be granted to the ident.
When a module is dropped, all the routines in the module will be dropped as well. See Using DROP and REVOKE for a discussion of CASCADE effects on modules and routines.
The operations that may be performed on a module are:
Refer to the Mimer SQL Reference Manual for a description of the SQL statements mentioned above, brief examples follow.
Examples:CREATE MODULE MY_MODULE DECLARE PROCEDURE P1 ... ; DECLARE PROCEDURE P2 ... ; DECLARE FUNCTION F1 ... ; ... END MODULE COMMENT ON MODULE MY_MODULE IS 'This is my example module' DROP MODULE MY_MODULE CASCADE
Upright Database Technology AB
Voice: +46 18 780 92 00
Fax: +46 18 780 92 40