Summary
Stored procedures in MySQL are a welcome and exciting addition to the 5.0 release. While there’s a lot of power, and perhaps some efficiency, in moving logic into your database, it’s important to consider if and how procedures fit into your existing application. Hasty decisions based on excitement to use cool technology usually lead to problems down the road.
As mentioned in the chapter, users should exercise caution in adopting the stored procedure functionality until the stability of the 5.0 server matches their environment requirements. For most users, waiting for the stable release is probably the best choice.
MySQL’s choice of SQL:2003 provides a good set of statements for developing procedures and a standard for potential inter-database procedure exchange. MySQL provides a good set of tools for creating, altering, dropping, and viewing procedures.
As MySQL developers continue to develop and flush out their implementation of stored procedures, we look forward to further developments of the stored procedure functionality and anxiously await the stable release of the 5.0 branch of MySQL.
In the next chapter, we’ll look at stored functions, another technology available in MySQL versions 5.0 and later.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
Rights and permissions
Copyright information
© 2005 Michael Kruckenberg and Jay Pipes
About this chapter
Cite this chapter
(2005). Stored Procedures. In: Pro MySQL. Apress. https://doi.org/10.1007/978-1-4302-0048-2_9
Download citation
DOI: https://doi.org/10.1007/978-1-4302-0048-2_9
Publisher Name: Apress
Print ISBN: 978-1-59059-505-3
Online ISBN: 978-1-4302-0048-2
eBook Packages: Professional and Applied ComputingProfessional and Applied Computing (R0)Apress Access Books