Creates a new stored procedure.
where procedure-definition is:
and parameter-definition is:
and values-clause is:
The procedure-name should follow the normal rules for naming database objects, see Naming Objects.
If procedure-name is specified in its unqualified form, the procedure will be created in the schema which has the same name as the current ident.
If procedure-name is specified in its fully qualified form (i.e. schema-name.procedure-name) the procedure will be created in the named schema (in this case, the current ident must be the creator of the specified schema).
The fully qualified procedure name must be used by all idents except the ident that has the same name as the schema to which the procedure belongs.
The parameter-name in the parameter-definition should follow the normal rules for naming SQL identifiers, see Naming Objects.
It is possible to create multiple procedures with the same name if they differ with regard to either the number of parameters, or the data type for the parameters. See Mimer SQL Programmer's Manual, Parameter Overloading for more information. Type precedence lists are found in Type Precedence Lists.
Each routine can be given a specific name, which must be unique within a schema. If no specific name is given, the system will generate a unique name. The specific name for a procedure can be retrieved by using the INFORMATION_SCHEMA views.
A specific name can be used in DROP, GRANT and REVOKE statements. It is particularly useful when dealing with procedures with parameter overloading. Instead of having to specify a list of data types, in order to distinguish the procedure, the specific name can be used.
The following mode values may be specified in a parameter-definition:
The parameter is effectively write-only, i.e. it can only be used as the target for an assignment and cannot be used in a value expression in the procedure. This type of parameter must be a variable in the procedure CALL statement
If neither IN, OUT nor INOUT is specified, then IN is implicit.
The permitted values for data-type, specified in parameter-definition, are described in Data Types in SQL Statements.
If a values-clause is specified, the procedure is created as a result set procedure. A result set procedure is a special type of procedure which returns a result-set and is called by being specified in a cursor declaration, see DECLARE CURSOR, rather than by using the CALL statement.
If neither DETERMINISTIC nor NOT DETERMINISTIC is specified, then NOT DETERMINISTIC is implicit.
If DETERMINISTIC is specified, then the procedure is guaranteed to produce the same result every time it is invoked with the same set of input values and repeated invocations of it can, therefore, be optimized.
The following access options may be specified:
- CONTAINS SQL
- READS SQL DATA
- MODIFIES SQL DATA
If neither CONTAINS SQL, READS SQL DATA nor MODIFIES SQL DATA is specified, then CONTAINS SQL is implicit.
A procedure created this way cannot be added to a module.
It is possible to create multiple procedures with the same name in a schema if the procedures have a different number of parameters or parameters with different data types.
It is not possible to create a synonym for a procedure name.
A parameter name must be unique within the procedure.
The ROW data type cannot be specified in parameter-definition or in a values-clause.
A result set procedure may only have parameters with mode IN.
A result set procedure or a routine invoked from within a result procedure, must not execute a COMMIT or ROLLBACK statement because this would interfere with the cursor used when the result set procedure is called.
If DETERMINISTIC is specified, the procedural-sql-statement of the procedure may not contain, or be, a reference to: SESSION_USER, CURRENT_DATE, CURRENT_PROGRAM, LOCALTIME or LOCALTIMESTAMP.
The option MODIFIES SQL DATA cannot be used for a result set procedure.
An ident must have EXECUTE privilege on the procedure in order to invoke it.
Refer to the Mimer SQL User's Manual, Creating Functions, Procedures, Triggers and Modules, for details on using the CREATE PROCEDURE statement in Mimer BSQL where the @ delimiter is required.
ExampleCREATE PROCEDURE res_proc (IN A INTEGER, IN B INTEGER) VALUES ( VARCHAR(32), INTEGER(10) ) AS ( CLIENT_NAME, CLIENT_ID ) READS SQL DATA BEGIN ... END;
For more information, see the Mimer SQL User's Manual, Creating Functions, Procedures, Triggers and Modules.
Mimer Information Technology AB
Voice: +46 18 780 92 00
Fax: +46 18 780 92 40