- 18 Stored Programs and Views
- 18.1 Defining Stored Programs
- 18.2 Using Stored Routines (Procedures and Functions)
- 18.3 Using Triggers
- 18.4 Using the Event Scheduler
- 18.5 Using Views
- 18.6 Binary Logging of Stored Programs
[+/-]
Stored routines (procedures and functions) are supported in MySQL 5.1. A stored routine is a set of SQL statements that can be stored in the server. Once this has been done, clients don't need to keep reissuing the individual statements but can refer to the stored routine instead.
Stored routines require the proc table in the
mysql database. This table is created during the
MySQL 5.1 installation procedure. If you are upgrading
to MySQL 5.1 from an earlier version, be sure to update
your grant tables to make sure that the proc
table exists. See Section 4.4.8, “mysql_upgrade — Check Tables for MySQL Upgrade”.
MySQL Enterprise. For expert advice on using stored procedures and functions subscribe to the MySQL Enterprise Monitor. For more information, see http://www.mysql.com/products/enterprise/advisors.html.
Stored routines can be particularly useful in certain situations:
When multiple client applications are written in different languages or work on different platforms, but need to perform the same database operations.
When security is paramount. Banks, for example, use stored procedures and functions for all common operations. This provides a consistent and secure environment, and routines can ensure that each operation is properly logged. In such a setup, applications and users would have no access to the database tables directly, but can only execute specific stored routines.
Stored routines can provide improved performance because less information needs to be sent between the server and the client. The tradeoff is that this does increase the load on the database server because more of the work is done on the server side and less is done on the client (application) side. Consider this if many client machines (such as Web servers) are serviced by only one or a few database servers.
Stored routines also allow you to have libraries of functions in the database server. This is a feature shared by modern application languages that allow such design internally (for example, by using classes). Using these client application language features is beneficial for the programmer even outside the scope of database use.
MySQL follows the SQL:2003 syntax for stored routines, which is also used by IBM's DB2.
The MySQL implementation of stored routines is still in progress. All syntax described here is supported and any limitations and extensions are documented where appropriate.
Additional resources
You may find the Stored Procedures User Forum of use when working with stored procedures and functions.
For answers to some commonly asked questions regarding stored routines in MySQL, see Section A.4, “MySQL 5.1 FAQ — Stored Procedures and Functions”.
There are some restrictions on the use of stored routines. See Section D.1, “Restrictions on Stored Routines, Triggers, and Events”.
Binary logging for stored routines takes place as described in Section 18.6, “Binary Logging of Stored Programs”.
User Comments
Add your own comment.