- A.4.1. Does MySQL support stored procedures and functions?
- A.4.2. Where can I find documentation for MySQL stored procedures and stored functions?
- A.4.3. Is there a discussion forum for MySQL stored procedures?
- A.4.4. Where can I find the ANSI SQL 2003 specification for stored procedures?
- A.4.5. How do you manage stored routines?
- A.4.6. Is there a way to view all stored procedures and stored functions in a given database?
- A.4.7. Where are stored procedures stored?
- A.4.8. Is it possible to group stored procedures or stored functions into packages?
- A.4.9. Can a stored procedure call another stored procedure?
- A.4.10. Can a stored procedure call a trigger?
- A.4.11. Can a stored procedure access tables?
- A.4.12. Do stored procedures have a statement for raising application errors?
- A.4.13. Do stored procedures provide exception handling?
- A.4.14. Can MySQL stored routines return result sets?
- A.4.15. Is WITH RECOMPILE supported for stored procedures?
- A.4.16. Is there a MySQL equivalent to using mod_plsql as a gateway on Apache to talk directly to a stored procedure in the database?
- A.4.17. Can I pass an array as input to a stored procedure?
- A.4.18. Can I pass a cursor as an IN parameter to a stored procedure?
- A.4.19. Can I return a cursor as an OUT parameter from a stored procedure?
- A.4.20. Can I print out a variable's value within a stored routine for debugging purposes?
- A.4.21. Can I commit or roll back transactions inside a stored procedure?
- A.4.22. Do MySQL stored procedures and functions work with replication?
- A.4.23. Are stored procedures and functions created on a replication source server replicated to a replica?
- A.4.24. How are actions that take place inside stored procedures and functions replicated?
- A.4.25. Are there special security requirements for using stored procedures and functions together with replication?
- A.4.26. What limitations exist for replicating stored procedure and function actions?
- A.4.27. Do the preceding limitations affect the ability of MySQL to do point-in-time recovery?
- A.4.28. What is being done to correct the aforementioned limitations?
A.4.1. | Does MySQL support stored procedures and functions? |
Yes. MySQL supports two types of stored routines, stored procedures, and stored functions. | |
A.4.2. | Where can I find documentation for MySQL stored procedures and stored functions? |
A.4.3. | Is there a discussion forum for MySQL stored procedures? |
Yes. See https://forums.mysql.com/list.php?98. | |
A.4.4. | Where can I find the ANSI SQL 2003 specification for stored procedures? |
Unfortunately, the official specifications are not freely available (ANSI makes them available for purchase). However, there are books, such as SQL-99 Complete, Really by Peter Gulutzan and Trudy Pelzer, that provide a comprehensive overview of the standard, including coverage of stored procedures. | |
A.4.5. | How do you manage stored routines? |
It is always good practice to use a clear naming scheme for your
stored routines. You can manage stored procedures with
| |
A.4.6. | Is there a way to view all stored procedures and stored functions in a given database? |
Yes. For a database named
For more information, see Section 28.3.30, “The INFORMATION_SCHEMA ROUTINES Table”.
The body of a stored routine can be viewed using
| |
A.4.7. | Where are stored procedures stored? |
Stored procedures are stored in the
You can also use | |
A.4.8. | Is it possible to group stored procedures or stored functions into packages? |
No. This is not supported in MySQL. | |
A.4.9. | Can a stored procedure call another stored procedure? |
Yes. | |
A.4.10. | Can a stored procedure call a trigger? |
A stored procedure can execute an SQL statement, such as an
| |
A.4.11. | Can a stored procedure access tables? |
Yes. A stored procedure can access one or more tables as required. | |
A.4.12. | Do stored procedures have a statement for raising application errors? |
Yes. MySQL implements the SQL standard | |
A.4.13. | Do stored procedures provide exception handling? |
MySQL implements | |
A.4.14. | Can MySQL stored routines return result sets? |
Stored procedures can, but stored functions
cannot. If you perform an ordinary
| |
A.4.15. |
Is |
No. | |
A.4.16. |
Is there a MySQL equivalent to using
|
There is no equivalent in MySQL. | |
A.4.17. | Can I pass an array as input to a stored procedure? |
No. | |
A.4.18. |
Can I pass a cursor as an |
Cursors are only available inside stored procedures. | |
A.4.19. |
Can I return a cursor as an |
Cursors are only available inside stored procedures. However, if
you do not open a cursor on a
| |
A.4.20. | Can I print out a variable's value within a stored routine for debugging purposes? |
Yes, you can do this in a stored procedure,
but not in a stored function. If you perform an ordinary
| |
A.4.21. | Can I commit or roll back transactions inside a stored procedure? |
Yes. However, you cannot perform transactional operations within a stored function. | |
A.4.22. | Do MySQL stored procedures and functions work with replication? |
Yes, standard actions carried out in stored procedures and functions are replicated from a replication source server to a replica. There are a few limitations that are described in detail in Section 27.7, “Stored Program Binary Logging”. | |
A.4.23. | Are stored procedures and functions created on a replication source server replicated to a replica? |
Yes, creation of stored procedures and functions carried out
through normal DDL statements on a replication source server are
replicated to a replica, so that the objects exist on both
servers. | |
A.4.24. | How are actions that take place inside stored procedures and functions replicated? |
MySQL records each DML event that occurs in a stored procedure and replicates those individual actions to a replica. The actual calls made to execute stored procedures are not replicated. Stored functions that change data are logged as function invocations, not as the DML events that occur inside each function. | |
A.4.25. | Are there special security requirements for using stored procedures and functions together with replication? |
Yes. Because a replica has authority to execute any statement read from a source's binary log, special security constraints exist for using stored functions with replication. If replication or binary logging in general (for the purpose of point-in-time recovery) is active, then MySQL DBAs have two security options open to them:
| |
A.4.26. | What limitations exist for replicating stored procedure and function actions? |
Nondeterministic (random) or time-based actions embedded in
stored procedures may not replicate properly. By their very
nature, randomly produced results are not predictable and cannot
be exactly reproduced; therefore, random actions replicated to a
replica do not mirror those performed on a source. Declaring
stored functions to be In addition, time-based actions cannot be reproduced on a replica because the timing of such actions in a stored procedure is not reproducible through the binary log used for replication. It records only DML events and does not factor in timing constraints.
Finally, nontransactional tables for which errors occur during
large DML actions (such as bulk inserts) may experience
replication issues in that a source may be partially updated
from DML activity, but no updates are done to the replica
because of the errors that occurred. A workaround is for a
function's DML actions to be carried out with the
| |
A.4.27. | Do the preceding limitations affect the ability of MySQL to do point-in-time recovery? |
The same limitations that affect replication do affect point-in-time recovery. | |
A.4.28. | What is being done to correct the aforementioned limitations? |
You can choose either statement-based replication or row-based replication. The original replication implementation is based on statement-based binary logging. Row-based binary logging resolves the limitations mentioned earlier.
Mixed replication is also
available (by starting the server with
For additional information, see Section 19.2.1, “Replication Formats”. |