These restrictions apply to the features described in Chapter 19, Stored Programs and Views.
Some of the restrictions noted here apply to all stored routines; that is, both to stored procedures and stored functions. There are also some restrictions specific to stored functions but not to stored procedures.
The restrictions for stored functions also apply to triggers. There are also some restrictions specific to triggers.
Stored routines cannot contain arbitrary SQL statements. The following statements are not allowed:
ALTER VIEW. (Before MySQL 5.1.21, this restriction is enforced only for stored functions.)
SQL prepared statements (
DEALLOCATE PREPARE) can be used in stored procedures, but not stored functions or triggers. Thus, stored functions and triggers cannot use dynamic SQL (where you construct statements as strings and then execute them).
SQL statements that are not permitted within prepared statements are also not permitted in stored routines. See Section 12.6, “SQL Syntax for Prepared Statements”, for a list of statements supported as prepared statements. Only the statements listed there are supported for stored routines, unless noted otherwise in Section 19.2, “Using Stored Routines (Procedures and Functions)”.
Before MySQL 5.1.4,
CALLstatements cannot be prepared. This is true both for server-side prepared statements and for SQL prepared statements.
Within all stored programs (stored procedures and functions, triggers, and events), the parser treats
BEGIN [WORK]as the beginning of a
BEGIN ... ENDblock. To begin a transaction in this context, use
The following additional statements or operations are not allowed within stored functions. They are allowed within stored procedures, except stored procedures that are invoked from within a stored function or trigger. For example, if you use
FLUSHin a stored procedure, that stored procedure cannot be called from a stored function or trigger.
Statements that perform explicit or implicit commit or rollback. Support for these statements is not required by the SQL standard, which states that each DBMS vendor may decide whether to allow them.
Statements that return a result set. This includes
SELECTstatements that do not have an
INTOclause and other statements such as
CHECK TABLE. A function can process a result set either with
SELECT ... INTOor by using a cursor and
FETCHstatements. See Section 184.108.40.206, “
SELECT ... INTOStatement”.
Stored functions cannot be used recursively.
A stored function or trigger cannot modify a table that is already being used (for reading or writing) by the statement that invoked the function or trigger.
If you refer to a temporary table multiple times in a stored function under different aliases, a
Can't reopen table: 'error occurs, even if the references occur in different statements within the function.
For triggers, the following additional restrictions apply:
Triggers currently are not activated by foreign key actions.
When using row-based replication, triggers on the slave are not activated by statements originating on the master. The triggers on the slave are activated when using statement-based replication. For more information, see Section 220.127.116.11, “Replication and Triggers”.
Triggers are not allowed on tables in the
The trigger cache does not detect when metadata of the underlying objects has changed. If a trigger uses a table and the table has changed since the trigger was loaded into the cache, the trigger operates using the outdated metadata.
The same identifier might be used for a routine parameter, a local variable, and a table column. Also, the same local variable name can be used in nested blocks. For example:
CREATE PROCEDURE p (i INT) BEGIN DECLARE i INT DEFAULT 0; SELECT i FROM t; BEGIN DECLARE i INT DEFAULT 1; SELECT i FROM t; END; END;
In such cases, the identifier is ambiguous and the following precedence rules apply:
A local variable takes precedence over a routine parameter or table column.
A routine parameter takes precedence over a table column.
A local variable in an inner block takes precedence over a local variable in an outer block.
The behavior that variables take precedence over table columns is nonstandard.
Use of stored routines can cause replication problems. This issue is discussed further in Section 19.7, “Binary Logging of Stored Programs”.
--replicate-wild-do-table=option applies to tables, views, and triggers. It does not apply to stored procedures and functions, or events. To filter statements operating on the latter objects, use one or more of the
INFORMATION_SCHEMAdoes not have a
PARAMETERStable until MySQL 5.5; this table allows stored routines or client applications to determine the names, types, and default values of parameters for stored routines. For releases without this
INFORMATION_SCHEMA.PARAMETERStable, to examine these types of metadata, you must use workarounds such as parsing the output of
SHOW CREATEstatements or the
param_listcolumn of the
param_listcontents can be processed from within a stored routine, unlike the output from
There are no stored routine debugging facilities.
The MySQL stored routine syntax is based on the SQL:2003 standard. The following items from that standard are not currently supported:
UNDOhandlers are not supported.
FORloops are not supported.
To prevent problems of interaction between sessions, when a client issues a statement, the server uses a snapshot of routines and triggers available for execution of the statement. That is, the server calculates a list of procedures, functions, and triggers that may be used during execution of the statement, loads them, and then proceeds to execute the statement. While the statement executes, it does not see changes to routines performed by other sessions.
For maximum concurrency, stored functions should minimize their side-effects; in particular, updating a table within a stored function can reduce concurrent operations on that table. A stored function acquires table locks before executing, to avoid inconsistency in the binary log due to mismatch of the order in which statements execute and when they appear in the log. When statement-based binary logging is used, statements that invoke a function are recorded rather than the statements executed within the function. Consequently, stored functions that update the same underlying tables do not execute in parallel. In contrast, stored procedures do not acquire table-level locks. All statements executed within stored procedures are written to the binary log, even for statement-based binary logging. See Section 19.7, “Binary Logging of Stored Programs”.
The following limitations are specific to the Event Scheduler:
In MySQL 5.1.6 only, any table referenced in an event's action statement must be fully qualified with the name of the schema in which it occurs (that is, as
Beginning with MySQL 5.1.8, event names are handled in case-insensitive fashion. For example, this means that you cannot have two events in the same database (and—prior to MySQL 5.1.12—with the same definer) with the names
If you have events created in MySQL 5.1.7 or earlier which are assigned to the same database and have the same definer, and whose names differ only with respect to lettercase, then you must rename these events to respect case-sensitive handling before upgrading to MySQL 5.1.8 or later.
Event timings using the intervals
YEAR_MONTHare resolved in months; those using any other interval are resolved in seconds. There is no way to cause events scheduled to occur at the same second to execute in a given order. In addition—due to rounding, the nature of threaded applications, and the fact that a nonzero length of time is required to create events and to signal their execution—events may be delayed by as much as 1 or 2 seconds. However, the time shown in the
LAST_EXECUTEDcolumn or the
last_executedcolumn is always accurate to within one second of the actual event execution time. (See also Bug#16522.)
Each execution of the statements contained in the body of an event takes place in a new connection; thus, these statements has no effect in a given user session on the server's statement counts such as
Com_insertthat are displayed by
SHOW STATUS. However, such counts are updated in the global scope. (Bug#16422)
Prior to MySQL 5.1.12, you could not view another user's events in the
INFORMATION_SCHEMA.EVENTStable. In other words, any query made against this table was treated as though it contained the condition
DEFINER = CURRENT_USER()in the
Events do not support times later than the end of the Unix Epoch; this is approximately the beginning of the year 2038. Prior to MySQL 5.1.8, handling in scheduled events of dates later than this was buggy; starting with MySQL 5.1.8, such dates are specifically disallowed by the Event Scheduler. (Bug#16396)
In MySQL 5.1.6,
SQL_MODEcolumn. Beginning with MySQL 5.1.7, the
SQL_MODEdisplayed is that in effect when the event was created.
In MySQL 5.1.6, the only way to drop or alter an event created by a user who was not the definer of that event was by manipulation of the
mysql.eventsystem table by the MySQL
rootuser or by another user with privileges on this table. Beginning with MySQL 5.1.7,
DROP USERdrops all events for which that user was the definer; also beginning with MySQL 5.1.7
DROP SCHEMAdrops all events associated with the dropped schema.
References to stored functions, user-defined functions, and tables in the
ON SCHEDULEclauses of
ALTER EVENTstatements are not supported. Beginning with MySQL 5.1.13, these sorts of references are disallowed. (See Bug#22830 for more information.)
Generally speaking, statements that are not permitted in stored routines or in SQL prepared statements are also not allowed in the body of an event. For more information, see Section 12.6, “SQL Syntax for Prepared Statements”.
When upgrading to MySQL 5.1.18 or 5.1.19 from a previous MySQL version where scheduled events were in use, the upgrade utilities mysql_upgrade and mysql_fix_privilege_tables do not accomodate changes in system tables relating to the Event Scheduler. This issue was fixed in MySQL 5.1.20 (see Bug#28521).
Stored routines and triggers in MySQL Cluster. Stored procedures, stored functions, and triggers are all supported by tables using the
NDBstorage engine; however, it is important to keep in mind that they do not propagate automatically between MySQL Servers acting as Cluster SQL nodes. This is because of the following:
Stored routine definitions are kept in tables in the
mysqlsystem database using the
MyISAMstorage engine, and so do not participate in clustering.
.TRGfiles containing trigger definitions are not read by the
NDBstorage engine, and are not copied between Cluster nodes.
Any stored routine or trigger that interacts with MySQL Cluster tables must be re-created by running the appropriate
CREATE FUNCTION, or
CREATE TRIGGERstatements on each MySQL Server that participates in the cluster where you wish to use the stored routine or trigger. Similarly, any changes to existing stored routines or triggers must be carried out explicitly on all Cluster SQL nodes, using the appropriate
DROPstatements on each MySQL Server accessing the cluster.
Do not attempt to work around the issue described in the first item mentioned previously by converting any
mysqldatabase tables to use the
NDBstorage engine. Altering the system tables in the
mysqldatabase is not supported and is very likely to produce undesirable results.