Choose your database:
AnySQL
MySQL
MS SQL Server
PostgreSQL
SQLite
Firebird
Oracle
SQL Anywhere
DB2
MaxDB

Subscribe to our news:
Partners
Testimonials
Giuseppe Maxia: "We are constantly testing everything related to MySQL world and MySQL Maestro is, so far, the best tool we have tried".
David Boccabella: "I have really!!!! enjoyed using SQL Maestro for MySQL over the past few months. It has become one of our major development tools for implementing intelligent into MySQL databases".

More

Add your opinion

SQL Maestro for MySQL online help

Prev Return to chapter overview Next

Specifying procedure options

Specify procedure options according to your needs. The detailed description is given below.
 

 

Name

The new procedure name as it was set on the previous step.

 

Owner

Defines the owner for the procedure. By default, only the owner of an object can perform various operations with the object. In order to allow other users to operate it, privileges must be granted. (However, users that have the superuser attribute can always access any object.)

 

Comment

Specify a comment for the procedure.

 

Data access (Contains SQL, No SQL, Reads SQL, Modifies SQL)

Select the clause to provide information about the nature of data use by the routine.

Contains SQL -

indicates that the routine does not contain statements that read or write data.

No SQL -

indicates that the routine contains no SQL statements.

Reads SQL -

indicates that the routine contains statements that read data, but not statements that write data.

Modifies SQL -

indicates that the routine contains statements that may write data.

These characteristics are advisory only. The server does not use them to constrain what kinds of statements a routine will be allowed to execute.

 

Deterministic

Check the option if the procedure always produces the same result for the same input parameters, and uncheck otherwise.

 

SQL security

Use the characteristic to specify whether the routine should be executed using the permissions of the user who creates the routine or the user who invokes it. The creator or invoker must have permission to access the database with which the routine is associated. It is necessary to have the EXECUTE privilege to be able to execute the routine. The user that must have this privilege is either the definer or invoker, depending on how the SQL security characteristic is set. The clause was added in MySQL 5.1.8.



Prev Return to chapter overview Next