Table of Contents
- 22.1 Defining Stored Programs
- 22.2 Using Stored Routines
- 22.3 Using Triggers
- 22.4 Using the Event Scheduler
- 22.5 Using Views
- 22.6 Stored Object Access Control
- 22.7 Stored Program Binary Logging
- 22.8 Restrictions on Stored Programs
- 22.9 Restrictions on Views
This chapter discusses stored database objects that are defined in terms of SQL code that is stored on the server for later execution.
Stored objects include these object types:
Stored procedure: An object created with
CREATE PROCEDUREand invoked using the
CALLstatement. A procedure does not have a return value but can modify its parameters for later inspection by the caller. It can also generate result sets to be returned to the client program.
Stored function: An object created with
CREATE FUNCTIONand used much like a built-in function. You invoke it in an expression and it returns a value during expression evaluation.
Trigger: An object created with
CREATE TRIGGERthat is associated with a table. A trigger is activated when a particular event occurs for the table, such as an insert or update.
Event: An object created with
CREATE EVENTand invoked by the server according to schedule.
View: An object created with
CREATE VIEWthat when referenced produces a result set. A view acts as a virtual table.
Terminology used in this document reflects the stored object hierarchy:
Stored routines include stored procedures and functions.
Stored programs include stored routines, triggers, and events.
Stored objects include stored programs and views.
This chapter describes how to use stored objects. The following sections provide additional information about SQL syntax for statements related to these objects, and about object processing:
For each object type, there are
DROPstatements that control which objects exist and how they are defined. See Section 13.1, “Data Definition Statements”.
Stored program definitions include a body that may use compound statements, loops, conditionals, and declared variables. See Section 13.6, “Compound Statements”.
Metadata changes to objects referred to by stored programs are detected and cause automatic reparsing of the affected statements when the program is next executed. For more information, see Section 8.10.4, “Caching of Prepared Statements and Stored Programs”.